HangfireIO / HangfireIO/Hangfire.Azure.ServiceBusQueue
LastHeartbeat SQL Issue
Open
- Dominant language
- C#
- Stars
- 59
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
I apologise if I'm not understanding this add on correctly, but I thought adding this would move the polling/heartbeat away from SQL and into AzureServiceBus.
However, I have this running on my site and noticed I've been getting a SQL time out error every now and then which is attributed to "update [HangFire].Server set LastHeartbeat = @now where Id = @id". I can see Hangfire smashing the SQL db every second?
I was under the impression that this removed the need for the constant SQL heartbeat?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.