[
https://issues.apache.org/jira/browse/CASSANDRA-19321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860873#comment-17860873
]
Caleb Rackliffe edited comment on CASSANDRA-19321 at 6/28/24 5:14 PM:
----------------------------------------------------------------------
bq. the node will be offline for some time
Fair. From a UX perspective, I guess there are a couple options:
{{nodetool accord mark_stale <host>}}, {{nodetool accord mark_active <host>}}
This might be the simplest, but if there are other states, that might get
unwieldy.
{{nodetool accord set_durability_status <host> [stale|active]}}
One command, specific, would accommodate other statuses...this might be my
pick. WDYT?
CC [~aweisberg] [~dcapwell]
was (Author: maedhroz):
bq. the node will be offline for some time
Fair. From a UX perspective, I guess there are a couple options:
{{nodetool accord mark_stale <host>}}, {{nodetool accord mark_active <host>}}
This might be the simplest, but if there are other states, that might get
unwieldy.
{{nodetool accord set_durability_status <host> [stale|active]}}
One command, would accommodate other statuses...this might be my pick. WDYT?
CC [~aweisberg] [~dcapwell]
> Accord: Command to mark replicas as “stale" for decommission
> ------------------------------------------------------------
>
> Key: CASSANDRA-19321
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19321
> Project: Cassandra
> Issue Type: Improvement
> Components: Accord
> Reporter: Benedict Elliott Smith
> Assignee: Caleb Rackliffe
> Priority: Normal
>
> So that other replicas may continue to cleanup their state, we must have an
> operator command for marking replicas as stale so that the remaining replicas
> do not wait for them to coordinate their durability status.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
