[
https://issues.apache.org/jira/browse/CASSANDRA-15160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17201873#comment-17201873
]
David Capwell commented on CASSANDRA-15160:
-------------------------------------------
Working on commit:
CI
3.0
Jenkins: https://ci-cassandra.apache.org/job/Cassandra-devbranch/41/
Circle CI:
https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-15160-cassandra-3.0-FE679B1E-281C-44F2-8C62-9EDA039FE4C3
3.11
Jenkins: https://ci-cassandra.apache.org/job/Cassandra-devbranch/42/
Circle CI:
https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-15160-cassandra-3.11-FE679B1E-281C-44F2-8C62-9EDA039FE4C3
trunk
Jenkins: https://ci-cassandra.apache.org/job/Cassandra-devbranch/43/
Circle CI:
https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-15160-trunk-FE679B1E-281C-44F2-8C62-9EDA039FE4C3
> 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: [email protected]
For additional commands, e-mail: [email protected]
