Bug 1154696 - Cron time out should be configurable.
Summary: Cron time out should be configurable.
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Image
Version: 2.x
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Michal Fojtik
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks: 1197873 1201055
TreeView+ depends on / blocked
 
Reported: 2014-10-20 14:38 UTC by Eric Rich
Modified: 2018-12-09 18:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
: 1197873 (view as bug list)
Environment:
Last Closed: 2016-07-13 14:05:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Eric Rich 2014-10-20 14:38:01 UTC
Description of problem:

Seeing issue where cron scripts take to long to run, and exceed the defined 9 second timeout. 

    Warning: daily cron run terminated as it exceeded max run time

How reproducible: Very

Steps to Reproduce:
1. Place a daily script that waits (sleeps) 10 second and returns True in the daily directory. 

Actual results:

Errors with message above

Expected results:

Should Error, however Cartridge owner should be able to configure this timeout value. 

Additional info:

https://github.com/openshift/origin-server/blob/b06ff29c484ff4f7c611f4c02955128c06916bc3/cartridges/openshift-origin-cartridge-cron/bin/cron_runjobs.sh#L95-L101

https://github.com/openshift/origin-server/blob/b06ff29c484ff4f7c611f4c02955128c06916bc3/cartridges/openshift-origin-cartridge-cron/bin/cron_runjobs.sh#L60-L68


Note You need to log in before you can comment on or make changes to this bug.