-
Notifications
You must be signed in to change notification settings - Fork 167
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
dirty read if the connection is not stable? #30
Comments
Dirty read tends to mean the reading uncommitted data. That shouldn't be possible, otherwise would be a bug. Please clarify what you mean by dirty read. |
Sorry, maybe I misunderstand.
Maybe it's a split-brain issue? |
Oh, of course stale reads can happen when not using Strong Consistency mode which isn't available in the community edition. Any time there are multiple masters in AP (split brain) the client could update either and read either. When the split brain clears, Aerospike will have to conflict resolve records updated on different masters. AP conflict resolution policies give you the option to either keep the latest update or the update which likely preserves the most history. In either case, updates not chosen will be lost. If you require stronger consistency guarantees and it is acceptable to sacrifice availability then you will need to look to the "Strong Consistency" feature in our Enterprise version. |
I see some logs about reading dirty data, and some logs about connection error.
Does the default read operation of client allow dirty read?
OS: Ubuntu 18.04.5
Version: Aerospike Community Edition build 5.6.0.5
Client: aerospike-client-c-5.2.0.ubuntu18.04.x86_64
The text was updated successfully, but these errors were encountered: