[
https://issues.apache.org/jira/browse/CASSANDRA-11418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17434518#comment-17434518
]
Brandon Williams commented on CASSANDRA-11418:
----------------------------------------------
In starting to write tests for this I realized that any node using the
hibernate state is going to show as replacing now too, such as a
coordinator-only node. Now is probably the time to also quit overloading
hibernate and have distinct states, and think about if we want to show those.
For now though, I'll work on a patch to break the states out and maintain the
current behavior of leaving those nodes hidden.
> Nodetool status should reflect hibernate/replacing states
> ---------------------------------------------------------
>
> Key: CASSANDRA-11418
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11418
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Observability, Tool/nodetool
> Reporter: Joel Knighton
> Assignee: Brandon Williams
> Priority: Low
> Fix For: 4.x
>
> Attachments: cassandra-11418-trunk
>
>
> Currently, the four options for state in nodetool status are
> joining/leaving/moving/normal.
> Joining nodes are determined based on bootstrap tokens, leaving nodes are
> based on leaving endpoints in TokenMetadata, moving nodes are based on moving
> endpoints in TokenMetadata.
> This means that a node will appear in normal state when going through a
> bootstrap with flag replace_address, which can be confusing to operators.
> We should add another state for hibernation/replacing to make this visible.
> This will require a way to get a list of all hibernating endpoints.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
