-
Notifications
You must be signed in to change notification settings - Fork 134
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
Cassandra 17594 attempt 2 #195
base: trunk
Are you sure you want to change the base?
Conversation
…_after_insert_wide_rows to wait for schema agreement
…e to downed nodes
test this please |
@@ -85,6 +85,9 @@ def test_force_repair_range_async_1(self): | |||
Collection<String> hosts, boolean fullRepair, | |||
String... columnFamilies) | |||
""" | |||
self.fixture_dtest_setup.ignore_log_patterns = [ | |||
'Nothing to repair for' | |||
] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you provide a bit of info when we see this case and why it is ok to ignore it, please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the log we generate when we skip repair due to no data (or no tables, etc.); this test does not write data, so skipping repair is the expected behavior
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added docs explaining why; these tests do repairs for a token range, but doesn't put in effort to make sure that there are partitions in that range, so the repair aborts.
The test is checking logging, which is done after we parse arguments and print them... if repair doesn't happen these tests don't really care.
No description provided.