If you are able to build Cassandra yourself, one other option is to
backport the ZstdCompressor patch. That's the route we opted to take.
I've put our Zstd patch against Cassandra 3.0, as backported by Joey
Lynch, up on Github [1].
Our experience with Zstd has been that it works wonders on many
Hello Shishir,
It shouldn't be necessary to take downtime to perform upgrades of a
Cassandra cluster. It sounds like the biggest issue you're facing is the
upgradesstables step. upgradesstables is not strictly necessary before a
Cassandra node re-enters the cluster to serve traffic; in my
erate the outliers I would use
>> that. I have to ask though, why are you not able to tolerate the outliers?
>> If you are reading and writing at quorum how is this impacting you?
>>
>> Regards,
>> Ariel
>>
>> On Sat, Oct 8, 2016, at 12:54 AM, Vladimir Yudovin
y things are off heap and C* can run with
>> >>>>>>>> CMS and
>> >>>>>>>> get 10 millisecond GCs all day long.
>> >>>>>>>>
>> >>>>>>>> You can go through tuning and hardware selection tr
>>>>>>>> the best hack around it is to code up your memory mapped file access
>>>>>>>> into JNI methods and find some way to get that to work. Right now if
>>>>>>>> you want to create a safe point a JNI method is the way to do it. The
>>>&
Hello cassandra-users,
I'm investigating an issue with JVMs taking a while to reach a safepoint. I'd
like the list's input on confirming my hypothesis and finding mitigations.
My hypothesis is that slow block devices are causing Cassandra's JVM to pause
completely while attempting to reach a
