I have a high frequency call that is being made and I am currently running 3 instances of Hangfire. My problem is that the data coming in can sometimes come in very quickly and a 2nd record that should really just be a patch to the first one will sometimes generate a duplicate row in the database because the 1st record didn’t finish in time. Is there anyway I can specify that a specific service can only run on one of the servers and that server has like a concurrency of 1 so only one job is executing at a time? I think this will then force the 2nd record to wait until the 1st record has finished and an update will be performed instead of another insert. Maybe someone has an idea how to accomplish this?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Prevent creation of duplicate hangfire server | 0 | 1410 | August 19, 2016 | |
| How to ensure that the same job will not run twice on the same time on multiple Physical Servers | 0 | 502 | May 17, 2023 | |
| Disable concurrent per server | 1 | 1147 | April 24, 2017 | |
| Different RecurringJobs executed at the same time creating duplicates | 1 | 1323 | May 23, 2017 | |
| Multiple instances avoid run same job multiple times | 0 | 897 | June 29, 2019 |