-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Jepsen][YCQL] Consistency check failure for improved bank workload #10328
Labels
area/docdb
YugabyteDB core features
area/ycql
Yugabyte CQL (YCQL)
kind/bug
This issue is a bug
kind/failing-test
Tests and testing infra
priority/medium
Medium priority issue
Comments
Link to full Jepsen logs https://drive.google.com/file/d/10_RJuDv-es4Yu35ekUVJVpw7LNOlJViY/view?usp=sharing |
20220405T111015.000Z.zip |
EDIT:
results in one transaction aborted. The end result state was still correct. Reproducing on YCQL:
And voila we hit the error:
|
yugabyte-ci
added
kind/bug
This issue is a bug
priority/medium
Medium priority issue
labels
Jun 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/docdb
YugabyteDB core features
area/ycql
Yugabyte CQL (YCQL)
kind/bug
This issue is a bug
kind/failing-test
Tests and testing infra
priority/medium
Medium priority issue
Jira Link: DB-923
I've extended coverage for YCQL bank workload, and now it also trigger inserts with same invariant.
Pull request with improved bank workload yugabyte/jepsen#55
Here is source code for inserts. On each dice == "insert" there is automatically incremented counter, so there is no concurrent runs here and each insert statement gets unique value, even when operation is failed.
May occur seven w/o any nemesis running
Jepsen validation log cut:
The text was updated successfully, but these errors were encountered: