[ https://issues.apache.org/jira/browse/CASSANDRA-15160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200837#comment-17200837 ]
Marcus Eriksson commented on CASSANDRA-15160: --------------------------------------------- ah nice catches, pushed fixes to the branches above + rebased the old dtest branch with the log greping fix. running cci with that dtest branch here: [3.0|https://app.circleci.com/pipelines/github/krummas/cassandra/538/workflows/c3cc5064-7c70-4873-8af6-268560883825] [3.11|https://app.circleci.com/pipelines/github/krummas/cassandra/540/workflows/83c6341a-b386-473d-ae71-bbf292fbc0c1] [trunk|https://app.circleci.com/pipelines/github/krummas/cassandra/539/workflows/a2cd8cc2-2072-49b7-a63e-5a99063a0ec9] > Add flag to ignore unreplicated keyspaces during repair > ------------------------------------------------------- > > Key: CASSANDRA-15160 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15160 > Project: Cassandra > Issue Type: Improvement > Components: Consistency/Repair > Reporter: Marcus Eriksson > Assignee: Marcus Eriksson > Priority: Normal > > When a repair is triggered on a node in 'dc2' for a keyspace with replication > factor {'dc1':3, 'dc2':0} we just ignore the repair in versions < 3. In 3.0+ > we fail the repair to make sure the operator does not think the keyspace is > fully repaired. > There might be tooling that relies on the old behaviour though, so we should > add a flag to ignore those unreplicated keyspaces > -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org