Hi Erick Thanks for your quick response. I have attached the full stacktrace which show exception during validation phase of table repair.
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 ? I am afraid that this may cause data resurrection (I have prior experience with same). Or you are pointing towards running scrub ? Kindly explain. 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) Regards Manish On Fri, Feb 14, 2020 at 11:11 AM Erick Ramirez <erick.rami...@datastax.com> wrote: > It will achieve the outcome you are after but I doubt anyone would > recommend that approach. It's like using a sledgehammer when an ordinary > hammer would suffice. And if you were hitting some bug then you'd run into > the same problem anyway. > > Can you post the full stack trace? It might provide us some clues as to > why you ran into the problem. Cheers! >
error.log
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
