Ok. that could be a possiblity, as this table has several static columns.
We have seen corrupt SStable errors before related to static columns, when we
dropped and recreated the column in this table.
We have an upgrade to 3.11 planned for later this year. so hoping these issues
will be resolved.
I've seen this stacktrace before:
WARN [SharedPool-Worker-1] 2020-05-18 10:22:29,152
> AbstractLocalAwareExecutorService.java:169 - Uncaught exception on thread
> Thread[SharedPool-Worker-1,5,main]: {}
> org.apache.cassandra.io.sstable.CorruptSSTableException: Corrupted:
> /opt/app/dir1/dir2/data
