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
Single task being run at a time regardless of how long the task takes.
I skimmed the code, I do not see where the lock is extended. Since redis locks have expiration, they need to be extended before the expiration hits. This should happen as long as the task is running. I think the locker interface should have an Extend method and should call it at certain interval before the lock expires.
The text was updated successfully, but these errors were encountered:
Describe the bug
When using a redis distributed locking, I still see the same task being run concurrently instead of one at a time.
To Reproduce
When I run the below code, I expect to see single task being run at a time because of the locking:
However, I see:
Version
Expected behavior
Single task being run at a time regardless of how long the task takes.
I skimmed the code, I do not see where the lock is extended. Since redis locks have expiration, they need to be extended before the expiration hits. This should happen as long as the task is running. I think the locker interface should have an
Extend
method and should call it at certain interval before the lock expires.The text was updated successfully, but these errors were encountered: