Skip to content
This repository has been archived by the owner on Nov 14, 2019. It is now read-only.

Be more robust about locking #19

Open
jtopper opened this issue Jan 21, 2015 · 1 comment
Open

Be more robust about locking #19

jtopper opened this issue Jan 21, 2015 · 1 comment

Comments

@jtopper
Copy link
Member

jtopper commented Jan 21, 2015

If a machine running zcollective is out of disc space, the lock file can be written but left at zero bytes. Be more robust in zcollective about handling invalid lock file state.

@mikesilky
Copy link
Contributor

ZCollective should also remove its lockfile if it terminates after an error. At present if an unexpected termination occurs, the lockfile is left in place.

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

No branches or pull requests

2 participants