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

Sql DeadLocks #2406

Open
McSaverInvestments opened this issue May 18, 2024 · 2 comments
Open

Sql DeadLocks #2406

McSaverInvestments opened this issue May 18, 2024 · 2 comments

Comments

@McSaverInvestments
Copy link

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.

image

image

image

@odinserj
Copy link
Member

Hm, do you have any deadlock graphs or at least resource names for these locks available? Also, what version of Hangfire.Core and Hangfire.SqlServer you are using? I haven't seen deadlocks in Hangfire for a long time already.

@McSaverInvestments
Copy link
Author

@odinserj Hello, I'm current using version 1.8.12. The only was I was able to get around this issue was reduce my work counts by a factor of 10. Any other idea or suggestions, thanks?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants