This release contains important fixes for SQL Server-based job storage to work better with sub-second polling (including TimeSpan.Zero for QueuePollingInterval) and properly send heartbeats for long-running jobs even if CLR’s Thread Pool is starved for long periods of time. It is also very likely that some problems related to high CPU usage and high number of fetching queries occurring after deploying new application version to IIS were also fixed (they are almost impossible to catch up, but same workaround already helped in the past).
rss feed Blog
Hangfire 1.7.28
-
by
@odinserj
- release, hangfire-core
- 0 Comments
- Edit on GitHub
Hangfire.Pro.Redis 2.8.13
-
by
@odinserj
- release, hangfire-pro
- 0 Comments
- Edit on GitHub
Maintenance release that fixes fatal error in connection manager after long period of reconnects and “ConnectionMultiplexer is not a Sentinel connection” error when using Hangfire.Pro.Redis.SEv2 package and trying to reconnect to Sentinel nodes after a failure.
Continue Reading →Hangfire.Pro.Redis 2.8.12
-
by
@odinserj
- release, hangfire-pro
- 0 Comments
- Edit on GitHub
This release fixed another problem which appear with large number of servers and relates to huge amount of “Removing server…” log messages after ungraceful shutdown. Now method which is responsible for removing inactive servers uses a distributed lock to avoid concurrency and produce less Redis commands and logs.
Continue Reading →Hangfire 1.8.0-beta4
-
by
@odinserj
- release, hangfire-core
- 0 Comments
- Edit on GitHub
The last preview version of the 1.8 release that adds support for dark mode for Dashboard UI (UseDarkModeSupportForDashboard configuration method should be called, since extension packages don’t support this mode yet), allow to use custom JavaScript and CSS files and improve default settings for SQL Server-based job storage to match the recommended options whenever possible.
Hangfire.Pro.Redis 2.8.11
-
by
@odinserj
- release, hangfire-pro
- 0 Comments
- Edit on GitHub
This release reduces the network bandwidth consumption in environments with hundreds of servers and hundreds of queues. There were unnecessary calls to SMEMBERS servers command in the FetchedJobsWatcher component responsible for fault detection, leading to ServerCount*QueueCount number calls to it.