Not sure about why repair is running, but we are also seeing the same
merkle tree issue in a mixed version cluster in which we have intentionally
started a repair against 2 upgraded DCs. We are currently researching, and
can post back if we find the issue, but also would appreciate if someone
has a
If anyone has any idea on what might cause this issue, it'd be great.
I don't understand what could trigger this exception.
But what I really can't understand is why repairs started to run suddenly
:-\
There's no cron job running, no active repair process, no Validation
compactions, Reaper is turn
Hi - i am trying (and failing) to get metricbeat working with
Cassandra/Jolokia and its a bit fiddly. Has anyone got an example yml
config for metricbeat that I could see?
Thanks,
Q
Hi All,
I'm having a bad situation where after upgrading 2 nodes (binaries only)
from 2.1.21 to 3.11.4 I'm getting a lot of warnings as follows:
AbstractLocalAwareExecutorService.java:167 - Uncaught exception on thread
Thread[ReadStage-5,5,main]: {}
java.lang.ArrayIndexOutOfBoundsException: null
Sure, you're welcome, glad to hear it worked! =)
Thanks for letting us know/reporting this back here, it might matter for
other people as well.
C*heers!
Alain
Le mer. 5 juin 2019 à 07:45, William R a écrit :
> Eventually after the reboot the decommission was cancelled. Thanks a lot
> for the
