You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jim Witschey (JIRA)" <ji...@apache.org> on 2015/06/02 23:04:49 UTC

[jira] [Updated] (CASSANDRA-9534) Repair data not always saved to system_distributed

     [ https://issues.apache.org/jira/browse/CASSANDRA-9534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Witschey updated CASSANDRA-9534:
------------------------------------
    Summary: Repair data not always saved to system_distributed  (was: Parent repair data not always saved to system_distributed)

> Repair data not always saved to system_distributed
> --------------------------------------------------
>
>                 Key: CASSANDRA-9534
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9534
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jim Witschey
>            Assignee: Marcus Eriksson
>             Fix For: 2.2.0 rc1
>
>
> About 1 out of 5 times, in a ccm-managed cluster, a repair doesn't write anything to the {{system_distributed.parent_repair_history}} table. [This dtest|https://github.com/riptano/cassandra-dtest/blob/master/repair_test.py#L296] reproduces the error on a 5-node cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)