[
https://issues.apache.org/jira/browse/CASSANDRA-15160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17196064#comment-17196064
]
Marcus Eriksson commented on CASSANDRA-15160:
---------------------------------------------
3.0: [patch|https://github.com/krummas/cassandra/commits/marcuse/15160-3.0],
[cci|https://app.circleci.com/pipelines/github/krummas/cassandra/514/workflows/df085bfb-d6df-434f-a6a6-846df6b9c9e0]
3.11: [patch|https://github.com/krummas/cassandra/commits/marcuse/15160-3.11],
[cci|https://app.circleci.com/pipelines/github/krummas/cassandra/513/workflows/ad7c154b-6463-433c-8008-4cfb09f75458]
trunk: [patch|https://github.com/krummas/cassandra/commits/marcuse/15160],
[cci|https://app.circleci.com/pipelines/github/krummas/cassandra/510/workflows/655d5f75-0193-4e61-8555-89f56f26cecd]
[~dcapwell] added your tests, could you have a quick look at the 3.0 patch as
it is slightly different from the trunk one? (the 3.11 is basically the same as
3.0)
> 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
