[jira] [Updated] (CASSANDRA-14294) forced incremental repairs should promote sstables if they can
[
https://issues.apache.org/jira/browse/CASSANDRA-14294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Eggleston updated CASSANDRA-14294:
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
fixed and committed as {{d4dfbb5c678415e63bb7cf7dfd78518dfa6ea7b9}} to trunk
and {{1888c4048b65c447733a2759f32472a7004eb46f}} to dtests master
> forced incremental repairs should promote sstables if they can
> --
>
> Key: CASSANDRA-14294
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14294
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Blake Eggleston
>Assignee: Blake Eggleston
>Priority: Minor
> Fix For: 4.0
>
>
> If you run an incremental repair with the {{--force}} flag, sstables won't be
> promoted to repaired. We want this to be the case if we're actually excluding
> replicas from the repair, but if all replicas are available for the repair,
> there's no reason not to promote
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14294) forced incremental repairs should promote sstables if they can
[
https://issues.apache.org/jira/browse/CASSANDRA-14294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-14294:
Status: Ready to Commit (was: Patch Available)
> forced incremental repairs should promote sstables if they can
> --
>
> Key: CASSANDRA-14294
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14294
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Blake Eggleston
>Assignee: Blake Eggleston
>Priority: Minor
> Fix For: 4.0
>
>
> If you run an incremental repair with the {{--force}} flag, sstables won't be
> promoted to repaired. We want this to be the case if we're actually excluding
> replicas from the repair, but if all replicas are available for the repair,
> there's no reason not to promote
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14294) forced incremental repairs should promote sstables if they can
[
https://issues.apache.org/jira/browse/CASSANDRA-14294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Eggleston updated CASSANDRA-14294:
Reviewer: Marcus Eriksson
Status: Patch Available (was: Open)
[branch|https://github.com/bdeggleston/cassandra/tree/14294]
[dtest-branch|https://github.com/bdeggleston/cassandra-dtest/tree/14294]
[tests|https://circleci.com/workflow-run/d12b5d38-ac2b-45d0-a6cd-a2d758c553bb]
> forced incremental repairs should promote sstables if they can
> --
>
> Key: CASSANDRA-14294
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14294
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Blake Eggleston
>Assignee: Blake Eggleston
>Priority: Minor
> Fix For: 4.0
>
>
> If you run an incremental repair with the {{--force}} flag, sstables won't be
> promoted to repaired. We want this to be the case if we're actually excluding
> replicas from the repair, but if all replicas are available for the repair,
> there's no reason not to promote
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
