The log shows that the the problem occurs when decompressing the SSTable but there's not much actionable info from it.
I would like to know what will be "ordinary hammer" in this case. Do you > want to suggest that deleting only corrupt sstable file ( in this case > mc-1234-big-*.db) would be suffice ? Exactly. I mean if it's just a one-off, why go through the trouble of blowing away all the files? :) I am afraid that this may cause data resurrection (I have prior experience > with same). Whoa! That's a long bow to draw. Sounds like there's more history to it. Note that i am not willing to run the entire node rebuild as it will take > lots of time due to presence of multiple big tables (I am keeping it as my > last option) I wasn't going to suggest that at all. I didn't like the sledge hammer approach. I certainly wouldn't recommend bringing in a wrecking ball. 😁 Cheers!
