Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The operation was unable to achieve a quorum during its retry window. #6

Open
divmgl opened this issue Feb 14, 2024 · 4 comments
Open

Comments

@divmgl
Copy link

divmgl commented Feb 14, 2024

Fantastic work on this and thank you.

Heads up that this library suffers from this same problem: mike-marcacci/node-redlock#291

@henk-mapli
Copy link

I'm also experiencing this problem.

@divmgl is right. node-redlock also has this issue. It was fixed in this PR, but a new version hasn't been released yet.

@Epick362
Copy link

I would also like to see this fixed.

@djMax
Copy link
Contributor

djMax commented Oct 10, 2024

Looking at that PR, this module already has all those changes in it.

@Epick362
Copy link

Apologies then but what is the reason for encountering these errors? Maybe I do not understand the nuances of the redlock algo but I do not understand the error message or how I could go about preventing it.
Some people in the linked repo mentioned increasing the retryCount * retryTimeout so that it covers the lock duration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants