We are seeing some exceptions after repair ran successfully.
We would like to know if compactions stop forever for the failed
ColumnFamily after the exception.
Cassandra Version 2.1.18
Stacktrace:
ERROR [CompactionExecutor:3] 2017-11-09 01:46:26,180
CassandraDaemon.java:231 - Exception in thre
ere’s a bit less risk to removing a single sstable
>
>
> --
> Jeff Jirsa
>
>
> On Nov 2, 2017, at 7:58 PM, sai krishnam raju potturi
> wrote:
>
> Yes. Move the corrupt sstable, and run a repair on this node, so that it
> gets in sync with it's peers.
>
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..
(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
==
On Wed, Jul 1, 2015 at 11:59 AM, Shashi Yachavaram
wrote:
> We have a 28 node cluster, out
t;java -version".
Thanks
shashi
On Thu, Jul 2, 2015 at 8:42 AM, Jason Wee wrote:
> you should check the network connectivity for this node and also its
> system average load. is that typo or literary what it is, cassandra
> 1.2.15.*1* and java 6 update *85* ?
>
>
>
>
We have a 28 node cluster, out of which only one node is experiencing
timeouts.
We thought it was the raid, but there are two other nodes on the same raid
without
any problem. Also The problem goes away if we reboot the node, and then
reappears
after seven days. The following hinted hand-off timeo
