[ 
https://issues.apache.org/jira/browse/CASSANDRA-21129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhijeet Dubey updated CASSANDRA-21129:
---------------------------------------
    Test and Documentation Plan: 
Unit tests, manual tests

 

bin/cassandra -f bin/cqlsh -e "CREATE KEYSPACE test_ks WITH replication = 
\{'class': 'SimpleStrategy', 'replication_factor': 1};" conda activate 
cassandra-oss bin/cqlsh -e "CREATE KEYSPACE test_ks WITH replication = 
\{'class': 'SimpleStrategy', 'replication_factor': 1};"

"CREATE KEYSPACE test_ks WITH replication = \{'class': 'SimpleStrategy', 
'replication_factor': 1};" bin/cqlsh -e "CREATE TABLE test_ks.test_table (id 
int PRIMARY KEY, name text);"

bin/nodetool flush system bin/sstablemetadatadump dump --data-dir data --all 
--verbose

bin/nodetool stopdaemon bin/sstablemetadatadump dump --data-dir data --all 
--verbose

bin/sstablemetadatadump dump --data-dir data --all --verbose --format json
                         Status: Patch Available  (was: In Progress)

> Tool to offline-dump the cluster metadata from an instance
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-21129
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21129
>             Project: Apache Cassandra
>          Issue Type: New Feature
>          Components: Transactional Cluster Metadata
>            Reporter: Abhijeet Dubey
>            Assignee: Abhijeet Dubey
>            Priority: Normal
>         Attachments: text-output.txt, to-string-dump-output.txt
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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.
>  
> 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to