cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-11728) Incremental repair fails with vnodes+lcs+multi-dc
Date Mon, 16 May 2016 14:06:13 GMT

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

Marcus Eriksson edited comment on CASSANDRA-11728 at 5/16/16 2:06 PM:
----------------------------------------------------------------------

I've been trying to reproduce this by running repair in a loop while running stress against
a 4 node vnode cluster with RF=3 without any "luck" - we are now trying to figure out what
repair service is doing differently.


was (Author: krummas):
I'v been trying to reproduce this by running repair in a loop while running stress against
a 4 node vnode cluster with RF=3 without any "luck" - we are now trying to figure out what
repair service is doing differently.

> Incremental repair fails with vnodes+lcs+multi-dc
> -------------------------------------------------
>
>                 Key: CASSANDRA-11728
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11728
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Nick Bailey
>
> Produced on 2.1.12
> We are seeing incremental repair fail with an error regarding creating multiple repair
sessions on overlapping sstables. This is happening in the following setup
> * 6 nodes
> * 2 Datacenters
> * Vnodes enabled
> * Leveled compaction on the relevant tables
> When STCS is used instead, we don't hit an issue. This is slightly related to https://issues.apache.org/jira/browse/CASSANDRA-11461,
except in this case OpsCenter repair service is running all repairs sequentially. Let me know
what other information we can provide. 



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

Mime
View raw message