Scheduled Job times out in 10 mins , How to increase the time out for Scheduled Jobs ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2016 04:50 AM
We have defined a Scheduled Job which calls a set of Script includes which queries REST messages and fills the CMDB tables from the response json we get , It takes more than 20 mins depending on the size of the configuration we are querying through REST messages .
But , the scheduled jobs timeout in 10 mins leaving the tables half filled . Right now we have broken down the Scheduled job into multiple scheduled jobs to fill all the tables as a workaround , Is there a better way to make sure our scheduled job never time out untill the whole process is over ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-13-2016 01:00 PM
If you're performing this action a limited number of times, have you tried running it as a Background Script?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-14-2016 04:36 AM
Hi,
I tested this on my developer instance with the REST quota rule.
First I added a copy of the Rest request timeout -quota rule. I gave it a lower order number.
Then I activated the glide.quota.manager.debug system property and did a large query into the incident table with cURL.
From debug data I could find that both rules were given a "Assigning quota" match to them. The transaction was though cancelled after 1 minute, even though the first rule had a max. duration time of 90 seconds. So at least two rules with identical conditions can not be selected based on the Order value.
Could you add some some conditions to your newly added rule (user value maybe)? Test it on dev/test and see how it goes.
Activate the glide property and I try too see how the rules are evaluated.
- Jan