-
Notifications
You must be signed in to change notification settings - Fork 34
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
Elle may miss two types of transaction anomalies: #21
Comments
Case 1 looks like a bug to me too! No idea why that one's happening--probably needs a test case and digging in to the version & txn graphs generated. Case 2, agreed, I think we can and should detect this. I'm not exactly sure whether this still qualifies as an internal anomaly--it's actually an external read! But because we assume writes are unique, we know it's reading a value from later in the same transaction, and we should still be able to pick that up in a single pass. If you want to work on this, take a look at |
We are going to publish some of our experimental results sooner or later. Based on your reply on the above two issues, would it be fair to say that Elle misses these two anomalies? |
Elle detects both of these anomalies. |
During my testing, I found the following two anomalies may be ignored by elle.
This case comes from transactional causal consistency:
Here is my REPL screenshot
It is obvious that there is a cycle and I think this cycle should be prohibited by stong-session-snapshot-isolation
This case is about the internal consistency for a transaction.
I know elle do something special for internal-cases for read-your-writes condition, but maybe elle does not check for the future read.
I would appreciate it if you could give a prompt reply.
Sincerely,
Young
The text was updated successfully, but these errors were encountered: