[ https://issues.apache.org/jira/browse/CASSANDRA-16768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-16768: ----------------------------------------- Change Category: Operability Complexity: Normal Component/s: Tool/sstable Fix Version/s: 3.11.x Status: Open (was: Triage Needed) > Add user defined SSTables optoin for nodetool scrub > --------------------------------------------------- > > Key: CASSANDRA-16768 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16768 > Project: Cassandra > Issue Type: Improvement > Components: Tool/sstable > Reporter: Scott Carey > Assignee: Scott Carey > Priority: Normal > Fix For: 3.11.x > > > nodetool scrub does not currently have an option to supply a user-defined > list of SSTables in the way that nodetool compact does. > This is a very big operational oversight. For example, if you have a > _single_ SSTable with a single corrupt block, you have to scrub the _entire_ > table in order to recover most of that table's data. On a large table (I > have an LCS table with 1.2TB) this takes _forever_ – to the point that we > decided that the best practice is to delete the entire file and repair the > range that the file contains, rather than scrub and repair only the range of > the bad blocks. > -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org