-
Notifications
You must be signed in to change notification settings - Fork 52
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
Add global locks to databases #10
Comments
I think |
@tsirif is referring to https://stackoverflow.com/a/11531818/3492631 |
Alright so that should not be how we lock the database. I haven't read the doc yet. We should read it when we try to address this issue. |
@bouthilx there's no other way to manually lock the database, although according to the MongoDB documentation, these operations cause |
I see. There is no way of locking over many updates, unless we use fsync or a retry loop like explained here. It seems it is just better to forget about atomic operations on many documents at a time. |
@bouthilx in that case, would it mean that the |
Some procedures might require atomic operations on many rows. For that we would need a lock on the database.
Regarding MongoDB, we can read in the doc that it supports many level of locks.
I don't know if global would be enough.
Here is a code snippet for mongodb from @dendisuhubdy
The text was updated successfully, but these errors were encountered: