Try run nodetool refresh or restarting Cassandra after removing the
corrupted file
On 4 Nov. 2017 03:54, "Shashi Yachavaram" wrote:
> When i tried to simulate this in the lab by moving files (mv
> KS-CF-ka-10143-* /tmp/files).
>
> Ran repair but it fails during snapshot creation. Where does it g
When i tried to simulate this in the lab by moving files (mv
KS-CF-ka-10143-* /tmp/files).
Ran repair but it fails during snapshot creation. Where does it get
the list of files and how do we update this list so we can get rid of
corrupted files, update list/index and move on with offline scrub/rep
This is not guaranteed to be safe
If the corrupted sstable has a tombstone past gc grace, and another sstable has
shadowed deleted data, removing the corrupt sstable will cause the data to come
back to life, and repair will spread it around the ring
If that’s problematic to you, you should cons
Yes. Move the corrupt sstable, and run a repair on this node, so that it
gets in sync with it's peers.
On Thu, Nov 2, 2017 at 6:12 PM, Shashi Yachavaram
wrote:
> We are cassandra 2.0.17 and have corrupted sstables. Ran offline
> sstablescrub but it fails with OOM. Increased the MAX_HEAP_SIZE to
We are cassandra 2.0.17 and have corrupted sstables. Ran offline
sstablescrub but it fails with OOM. Increased the MAX_HEAP_SIZE to 8G it
still fails.
Can we move the corrupted sstable file and rerun sstablescrub followed by
repair.
-shashi..
