You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
@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?
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.
The text was updated successfully, but these errors were encountered: