[
https://issues.apache.org/jira/browse/CASSANDRA-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522395#comment-14522395
]
Tyler Hobbs commented on CASSANDRA-5839:
----------------------------------------
It looks like this is breaking the dtests in
{{sstable_generation_loading_tests}}:
http://cassci.datastax.com/job/trunk_dtest/57/testReport/sstable_generation_loading_test/
When the cluster is restarted, the nodes are failing to log a message about the
other node being {{now UP}}. I simplified the dtests down to just this to
bisect:
{noformat}
def simple_test(self):
cluster = self.cluster
cluster.populate(2).start()
[node1, node2] = cluster.nodelist()
node1.nodetool('drain')
node1.stop()
node2.nodetool('drain')
node2.stop()
cluster.clear()
cluster.start()
{noformat}
and bisect pointed to this commit (I double-checked by hand).
> 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)
