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.

Sign up for GitHub

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

Jump to bottom

lmdb.LockError on multi-node, Dockerized clusters #2011

Open
oberstet opened this issue May 6, 2022 · 1 comment
Open

lmdb.LockError on multi-node, Dockerized clusters #2011

oberstet opened this issue May 6, 2022 · 1 comment
Labels
bug core needs-investigation

Comments

@oberstet
Copy link
Contributor

oberstet commented May 6, 2022 •
edited
Loading

On Dockerized clusters that share zLMDB databases, eg for persistent cookie stores, when a cluster boots up it sometimes fails with lmdb.LockError

https://gist.github.com/oberstet/fdebff3a9102e614b00c77f3d9757cff

Crucially: I never saw that on non-Dockerized clusters

However, in any case, this code seems to be sth we can and should improve https://github.com/crossbario/zlmdb/blob/2ebd65a51e0ba48fb72a354bbb72591d3d27d8e4/zlmdb/_database.py#L337

Plus, try to understand what's going on. Eg what exactly does Docker change in terms of Posix filesystem semantics?

We should also test with "NFS" in the mix .. that is, a concrete NFS implementation such as Linux and AWS EFS
@oberstet oberstet mentioned this issue May 6, 2022
Open
@oberstet
Copy link
Contributor Author

oberstet commented May 6, 2022

see also crossbario/zlmdb#53

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug core needs-investigation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@oberstet