You need to stop C* in order to run the offline sstable scrub utility. That's why it's referred to as "offline". :)
Do you have any idea on what caused the corruption? It's highly unusual that you're thinking of removing all the files for just one table. Typically if the corruption was a result of a faulty disk or hardware failure, it wouldn't be isolated to just one table. If you provide a bit more background information, we would be able to give you a better response. Cheers! Erick Ramirez | Developer Relations erick.rami...@datastax.com | datastax.com <http://www.datastax.com> <https://www.linkedin.com/company/datastax> <https://www.facebook.com/datastax> <https://twitter.com/datastax> <http://feeds.feedburner.com/datastax> <https://github.com/datastax/> <https://www.datastax.com/accelerate> On Fri, 14 Feb 2020 at 04:39, manish khandelwal < manishkhandelwa...@gmail.com> wrote: > Hi > > I see a corrupt SSTable in one of my keyspace table on one node. Cluster > is 3 nodes with replication 3. Cassandra version is 3.11.2. > I am thinking on following lines to resolve the corrupt SSTable issue. > 1. Run nodetool scrub. > 2. If step 1 fails, run offline sstabablescrub. > 3. If step 2 fails, stop node. Remove all SSTables from problematic > table.Start the node and run full repair on table.I am removing all > SSTABLES of the particular table so as to avoid resurrection of data or any > data corruption. > > I would like to know are there any side effects of executing step 3 if > step 1 and step 2 fails. > > Regards > Manish > > > > >
