[
https://issues.apache.org/jira/browse/CASSANDRA-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526735#comment-14526735
]
Marcus Eriksson commented on CASSANDRA-5839:
--------------------------------------------
Looks like it could be an issue with announcing the new keyspace
system_distributed too soon after announcing system_traces (adding a 1s sleep
before announcing the second ks fixes it). But why would it only break if we
cluster.clear() and then restart?
also, modifying the test to do:
{code} node1.clear(clear_all=True)
node2.clear(clear_all=True){code} instead of {{cluster.clear()}} makes the
simple_test above pass (clear_all=True also removes log files)
I'll keep digging...
> Save repair data to system table
> --------------------------------
>
> Key: CASSANDRA-5839
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5839
> Project: Cassandra
> Issue Type: New Feature
> Components: Core, Tools
> Reporter: Jonathan Ellis
> Assignee: Marcus Eriksson
> Priority: Minor
> Fix For: 3.0
>
> Attachments: 0001-5839.patch, 2.0.4-5839-draft.patch,
> 2.0.6-5839-v2.patch
>
>
> As noted in CASSANDRA-2405, it would be useful to store repair results,
> particularly with sub-range repair available (CASSANDRA-5280).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
