-
Heavy I/O bound background jobs consume worker thread inefficiently – instead of doing the real work they wait for the completion of I/O operation(s). Currently if an application has a lot of such bac…
-
Hello!
**Version of Hangfire.Core**: 1.6.19.0
**Storage package**: Hangfire.SqlServer
**Configuration logic**: Asp .Net core 2.0
**What happen:**
1.- Website cannot start ( not /hangfire, not m…
-
## Idea
I'd like to propose implementing way for configuring custom table names that Hangfire uses in underlying SQL Server storage.
## How do I see it
`SqlServerStorageOptions` should make pos…
-
Hangfire.Core version: **1.7.24**
Storage package: **Hangfire.Mongo v0.7.22**
**_Expected_**:
* The value reported in the badge of the `Succeeded` left navigation to match the value reported as t…
-
I get the following exception when calling `PerformContext.WriteLine` in a multi-threaded context. First, exception (1) is thrown once, followed by many throws of exception (2) for each other thread t…
-
Not sure if you guys have tried the new version, but we had to revert to 1.9.3 because it would not complete jobs.
Related to this work: https://github.com/marcoCasamento/Hangfire.Redis.StackExchan…
-
Hangfire.Core: v1.7.8
Hangfire.PostgreSql: v1.6.3
Hangfire.Pro: v2.2.1
Dotnet Core: v2.2
Possible deadlock in the postgresql storage connector.
I don't see anything when using Trace logging f…
-
It’s a wonderful extension and I totally love it.
However, recently under load, getting a lot of time out exceptions due to this.
Stack trace:
````
System.Data.SqlClient.SqlException
Exec…
-
I am using Hangfire 1.7.3 and Hangfire.PostgreSql 1.6.0 on ASPNET Core 2.2.300. And I have a 24/7 RecurringJob running every minute with default 20 workers on server along with other jobs. This job ca…
-
I'm running SQL 2016 as the storage and can see in the Set table console logs for example Key "console:61a3d4c0e711404025"
I can also confirm in the Hash table these are correct, however when runni…