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

Support a command line option to not allow acquiring new locks the first n seconds after reboot. #28

Open
pacman82 opened this issue Apr 19, 2020 · 0 comments

Comments

@pacman82
Copy link
Owner

Imagine the server should crash or be killed and rebooted. In this case the clients are going to restore their acquired locks. However they will do so only after their heartbeat receives the Unknown Peer error from the server. Should to many clients acquire new locks, before this happens, the whole system runs at risk of increasing the semaphore count beyond max. While this is intentionally supported, it would be nice if we could delay handing out new locks after a server reboot. Specifically increasing it two a time somewhat longer than the heartbeat interval should make incrementing the semaphore count beyond max nearly impossible.

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

1 participant