HangfireIO / HangfireIO/Hangfire
Sql DeadLocks
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 10.1k
- Forks
- 1.8k
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 1
Description
Im currently running scheme 9, I'm seeing a lot of xp_userlock and (@id bigint)select InvocationData, StateName, Arguments, CreatedAt from [HangFire].Job with (readcommittedlock, forceseek) where Id = @id select Name, Value from [HangFire].JobParameter with (forceseek) where JobId = @id
that are taking a long time to complete and creating deadlock. I'm only try to process about 300 jobs at the moment.
This is my current setup.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report using schema 9 and the shown setup, while capturing SQL Server deadlock information for the xp_userlock activity. Inspect the Job and JobParameter queries and compare their locking behavior while processing about 300 jobs. Done means the cause is identified and the reported long-running queries no longer create deadlocks under the same workload.
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
- 25/100