[ https://issues.apache.org/jira/browse/CASSANDRA-17568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526109#comment-17526109 ]
Stefan Miklosovic commented on CASSANDRA-17568: ----------------------------------------------- Thats exactly right. Server should process it all when its file-system is involved, indeed. I made a mistake here not detecting it does not make a lot of sense as I was thinking too much "locally". > Implement nodetool command to list data directories of existing tables > ---------------------------------------------------------------------- > > Key: CASSANDRA-17568 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17568 > Project: Cassandra > Issue Type: New Feature > Components: Tool/nodetool > Reporter: Tibor Repasi > Assignee: Tibor Repasi > Priority: Normal > Fix For: 4.x > > Time Spent: 9h 10m > Remaining Estimate: 0h > > When a table is created, dropped and re-created with the same name, > directories remain within data paths. Operators may be challenged finding out > which directories belong to existing tables and which may be subject to > removal. However, the information is available in CQL as well as in MBeans > via JMX, a convenient access to this information is still missing. > My proposal is a new nodetool subcommand allowing to list data paths of all > existing tables. > {code} > % bin/nodetool datapaths -- example > Keyspace : example > Table : test > Paths : > > /var/lib/cassandra/data/example/test-02f5b8d0c0e311ecb327ff24df5ab301 > ---------------- > {code} -- This message was sent by Atlassian Jira (v8.20.7#820007) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org