dracarys09 opened a new pull request, #4581:
URL: https://github.com/apache/cassandra/pull/4581
When a Cassandra node fails to start due to Transactional Cluster Metadata
(TCM/CEP-21) corruption or issues, operators need a way to inspect the cluster
metadata state offline without starting the node. The existing tools (nodetool,
cqlsh) require a running node, leaving operators blind when debugging startup
failures.
With CEP-21 (Transactional Cluster Metadata), cluster metadata is stored in
system tables:
* system.local_metadata_log - Contains transformation entries (epoch ->
transformation)
* system.metadata_snapshots - Contains periodic snapshots of ClusterMetadata
When a node fails to start due to TCM corruption or inconsistencies,
operators have no way to inspect the metadata state without a running node.
This tool fills that gap by reading directly from SSTables.
Thanks for sending a pull request! Here are some tips if you're new here:
* Ensure you have added or run the [appropriate
tests](https://cassandra.apache.org/_/development/testing.html) for your PR.
* Be sure to keep the PR description updated to reflect all changes.
* Write your PR title to summarize what this PR proposes.
* If possible, provide a concise example to reproduce the issue for a
faster review.
* Read our [contributor
guidelines](https://cassandra.apache.org/_/development/index.html)
* If you're making a documentation change, see our [guide to documentation
contribution](https://cassandra.apache.org/_/development/documentation.html)
Commit messages should follow the following format:
```
<One sentence description, usually Jira title or CHANGES.txt summary>
<Optional lengthier description (context on patch)>
patch by <Authors>; reviewed by <Reviewers> for CASSANDRA-#####
Co-authored-by: Name1 <email1>
Co-authored-by: Name2 <email2>
```
The [Cassandra
Jira](https://issues.apache.org/jira/projects/CASSANDRA/issues/)
--
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]
