Hangfire: In RecurringJob , Job [A] does not completed and still running, and then a new job [A] starts, it maybe makes two jobs processing the same data.

[ccccccmd]

In RecurringJob , Job [A] does not completed and still running, and then a new job [A] starts, it maybe makes two jobs processing the same data. what should I do to deal with this situation. for i can't handle the job's running time,so i can't set a reasonable Corn

[dcorbett-fivebridgesllc]

Check the discussion on this page, covering the topic:

http://docs.hangfire.io/en/latest/background-methods/performing-recurrent-tasks.html

It appears these two attributes deal with this situation:

[DisableConcurrentExecution(5)],
[AutomaticRetry(Attempts = 0, LogEvents = false, OnAttemptsExceeded = AttemptsExceededAction.Delete)]

I haven't yet tried recurring jobs myself... So I can't guarantee they work.

[ccccccmd]

@dcorbett-fivebridgesllc
thanks a lot! i'll try it.

[odinserj]

@ccccccmd, don't use it, please see #1053. @dcorbett-fivebridgesllc, looks like you are using them, and looks like they do cause your issues with non-processed queues, please see #1053 too.

[dcorbett-fivebridgesllc]

Any issues I have are not related to use of DisableConcurrentExecution. Not using recurring jobs, and not using this attribute. I had just seen the thread with a solution, and shared it here.

[henrik-donuts]

I created a new MaxConcurrentExecutions filter that handles this correctly: https://gist.github.com/henrik-donuts/0e38af74f95ebfce103fd2568d3455f7