Open alessandro-sorint opened 3 years ago
We are working to an implementation: https://github.com/sorintlab/stolon/pull/813
@alessandro-sorint you should investigate why your nfs server/client doesn't support locking. NFSv4 should have it enabled by default.
We could add a flag to disable locking but it should be marked as dangerous in the description since it's a workaround on underlying storage issues and it'll cause data corruptions if two keepers are concurrently running with the same data dir.
Tanks @sgotti we use in our configuration volumes different for evry keeper, so I think it's not a problem to remove the file locking
Tanks @sgotti we use in our configuration volumes different for evry keeper, so I think it's not a problem to remove the file locking
There's always the probability that two keepers will run on the same data dir for multiple reasons (wrong configuration, user error etc...). The real solution is to fix the filesystem locking issues but if it's not possible I'm ok to add an option but with a big warning like explained above.
We did it! https://github.com/sorintlab/stolon/pull/817
Is it enough clear the message of warning? Should we add a log of warning? Thanks
I had the same error when one of the nodes was disconnected and reconnected.
What would you like to be added: We would like to add a flag to avoid the lock on data dir because the syscall F_SETLK doesnt't work.
Why is this needed: We have tryed to deploy a pod with stolon keeper so defined:
We had this log errors: