HangfireIO / HangfireIO/Hangfire
Recurring jobs do not finish after upgrading from 1.8.6 to 1.8.11 (in combination with DynamicJobs)
- Dominant language
- C#
- Stars
- 10.1k
- Forks
- 1.8k
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 1
Description
We experience the following issue after we upgraded our Hangfire versions to 1.8.11: jobs never leave the **Processing** state, even though the C# code that the job itself executes has finished. We use Hangfire in combination with Hangfire.DynamicJobs to use a single SQL Server database with multiple servers, which we upgraded to 0.2.0 together with the 1.8.11 upgrade of the main Hangfire packages.
Contributor guide
Research direction
Start by reproducing the upgrade from Hangfire 1.8.6 to 1.8.11 with Hangfire.DynamicJobs 0.2.0, using one SQL Server database and multiple servers. Compare recurring-job processing before and after the upgrade; done means the C# job finishes and the job leaves the Processing state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100