cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Witschey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9534) Parent repair data not always saved to system_distributed
Date Tue, 02 Jun 2015 21:03:49 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569762#comment-14569762
] 

Jim Witschey commented on CASSANDRA-9534:
-----------------------------------------

If [this dtest failure|http://cassci.datastax.com/view/trunk/job/trunk_dtest/200/testReport/repair_test/TestRepairDataSystemTable/repair_table_test/]
is any indication, the regular repair history table is also not populated sometimes.

> Parent 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)

Mime
View raw message