You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The FetchedJobsWatcher and FetchedJobsWatcherOptions.JobTimeout are telling Hangfire to abort tasks after 15 minutes. I have several tasks that can run 30-45 minutes, but they're being aborted (Hangfire.Server.JobAbortedException) after 15 minutes and re-queued, and the FetchedJobsWatcherOptions is internal, so I can't specify a new timeout value.
It's also very difficult to figure out this is happening. I actually had to sit in front of the debugger for 15 minutes, hah. But, then I noticed it's pretty clear in the logs:
1 timed out jobs were found in the 'default' queue and re-queued.
Is there a reason why the FetchedJobsWatcherOptions.JobTimeout is set to 15 minutes? Would it break anything to set it to 1 hour, or even 1 day? If not, then I would consider this a bug, since it essentially prohibits tasks running longer than 15 minutes when using Redis.
I have a similar issue with the ServerWatchdogOptions (#159). I think these options classes should be exposed via the API, because It would add a lot of flexibility. So, in the FetchedJobsWatcher case I would like to be able to use this:
new RedisStorageOptions()
{
JobTimeout = TimeSpan.FromHours(1)
}
The text was updated successfully, but these errors were encountered:
sjwoodard
changed the title
Redis storage prohibits jobs from running longer than 15 minutes
Redis.FetchedJobsWatcher prohibits jobs from running longer than 15 minutes
Jul 14, 2014
The
FetchedJobsWatcher
andFetchedJobsWatcherOptions.JobTimeout
are telling Hangfire to abort tasks after 15 minutes. I have several tasks that can run 30-45 minutes, but they're being aborted (Hangfire.Server.JobAbortedException
) after 15 minutes and re-queued, and theFetchedJobsWatcherOptions
isinternal
, so I can't specify a new timeout value.It's also very difficult to figure out this is happening. I actually had to sit in front of the debugger for 15 minutes, hah. But, then I noticed it's pretty clear in the logs:
1 timed out jobs were found in the 'default' queue and re-queued.
Is there a reason why the
FetchedJobsWatcherOptions.JobTimeout
is set to 15 minutes? Would it break anything to set it to 1 hour, or even 1 day? If not, then I would consider this a bug, since it essentially prohibits tasks running longer than 15 minutes when using Redis.I have a similar issue with the
ServerWatchdogOptions
(#159). I think these options classes should be exposed via the API, because It would add a lot of flexibility. So, in theFetchedJobsWatcher
case I would like to be able to use this:The text was updated successfully, but these errors were encountered: