jaydeepkumar1984 opened a new pull request, #2374: URL: https://github.com/apache/cassandra/pull/2374
``` A new nodetool/JMX command that tells whether node's decommission failed or not Currently, when a node is being decommissioned and if any failure happens, then an exception is thrown back to the caller. But Cassandra's decommission takes considerable time ranging from minutes to hours to days. There are various scenarios in that the caller may need to probe the status again: The caller times out It is not possible to keep the caller hanging for such a long time And If the caller does not know what happened internally, then it cannot retry, etc., leading to other issues. So, in this ticket, I am going to add a new nodetool/JMX command that can be invoked by the caller anytime, and it will return the correct status. It might look like a smaller change, but when we need to operate Cassandra at scale in a large-scale fleet, then this becomes a bottleneck and require constant operator intervention. patch by Jaydeepkumar Chovatia <[email protected]>; reviewed by <Reviewers> for CASSANDRA-18555 Co-authored-by: Jaydeepkumar Chovatia <[email protected]> ``` The [Cassandra Jira](https://issues.apache.org/jira/browse/CASSANDRA-18555) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
