Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redis.FetchedJobsWatcher prohibits jobs from running longer than 15 minutes #164

Closed
sjwoodard opened this issue Jul 14, 2014 · 0 comments
Closed
Labels
Milestone

Comments

@sjwoodard
Copy link

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)
}
@sjwoodard 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
@odinserj odinserj added the bug label Aug 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants