-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
dtest test_resetlocalschema_api_issue_7811 AssertionError: Schema versions are different on the nodes #11643
Comments
I bisected this issue to a3356e8 Cc @fee-mendes @nyh |
I think this change inadvertently fixed #7811 |
I can't reproduce it. Well, at least not an error. :-) N1:
N2:
CREATE KEYSPACE ks WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 2};
CREATE TABLE ks.cf (pk int PRIMARY KEY) WITH compaction = {'class': 'TimeWindowCompactionStrategy', 'compaction_window_unit': 'NOPE'};
CREATE TABLE ks.cf (pk int PRIMARY KEY) WITH compaction = {'class': 'TimeWindowCompactionStrategy'}; Manual run:
|
Yes and no. There are other compaction strategies which aren't verified. |
I'll adjust the test to support both cases |
@tgrabiec please look into this. |
There's a missing backport. |
Lack of #14710 could explain it. relocal schema invokes schema merge path now, so if we corrupted schema so that the table is on disk but not in database object, relocal schema will fail the same way "create table" would fail. |
But we have now d96440e - so I'm unsure why we still see this. |
This is seen consistently since https://jenkins.scylladb.com/view/master/job/scylla-master/job/dtest-daily-release/93/testReport/junit/nodetool_additional_test/TestNodetool/Run_Dtest_Parallel_Cloud_Machines___FullDtest___full_split004___test_resetlocalschema_api_issue_7811/
scylla version 2a74a00
scylladb/scylla-dtest@ef8537c64f22a9df05137369cc24212ee717f3cd
I'm not sure what could have introduced the regression.
last consistently passed with 6799e76
scylladb/scylla-dtest@250ea614e947429463538d749655782e13ba73e7
The text was updated successfully, but these errors were encountered: