[
https://issues.apache.org/jira/browse/CASSANDRA-17407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502731#comment-17502731
]
Berenguer Blasi commented on CASSANDRA-17407:
---------------------------------------------
[~Jan Karlsson] notice your 3.11 patch link above points to the dtest repro.
But I checked the code on the PR and LGTM. Also notice your circle failures,
these are because you need higher resources than they are available on the free
tier. Don't worry we'll run them for you.
LGTM +1. Adding {{@since}} and a pre-merge CI run can be done on commit imo.
> Validate existence of DCs when repairing
> ----------------------------------------
>
> Key: CASSANDRA-17407
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17407
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Repair
> Reporter: Jan Karlsson
> Assignee: Jan Karlsson
> Priority: Normal
> Fix For: 3.11.x, 4.0.x
>
>
> With the new validation of data centers in the replication factor, it might
> be good to give similar treatment to repair.
> Currently the behavior of the --in-dc flag only validates that it contains
> the local data center.
> If a list is given containing nonexistent data centers, the repair will pass
> without errors or warning as long as this list also contains the local data
> center.
> My suggestion would be to validate all the data centers and give an error
> when a nonexistent data center is given.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
