[CASSANDRA-18749] Expose bootstrap failure state via JMX

• Type: Task
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.0-alpha1, 5.0, 5.1
• Component/s: Observability/JMX
• Change Category: Operability
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/acb4993cd0545ba4ce7bbb0a506c0cf46a0ac5ef

Test and Documentation Plan

CI

• Assignee: Jaydeepkumar Chovatia
• Reporter: Jaydeepkumar Chovatia

Authors

Jaydeepkumar Chovatia

Reviewers

Brandon Williams, Stefan Miklosovic

• Created: 13/Aug/23 08:47
• Updated: 12/Sep/23 13:03
• Resolved: 20/Aug/23 17:20

Description

Similar to how we have exposed a node's decommissioning via JMX as part of CASSANDRA-18555.

This ticket will address the same when a new node joins (i.e., bootstrap). 

When a node is bootstrapped, an error is thrown back to the caller if any failure happens.

But Cassandra's bootstrap 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, a new nodetool/JMX option will be exposed that can be invoked by the caller anytime, and it will return the correct status.

Issue Links

• is related to: CASSANDRA-18555 Expose decommission state to nodetool info
• links to: Github
• links to: GitHub Pull Request #2596