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 ki
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 experien
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 wrote:
>>
>> Hi Josh,
>>
>> >Running with increased heap
gt;> get 10 millisecond GCs all day long.
>> >>>>>>>>
>> >>>>>>>> You can go through tuning and hardware selection try to get more
>> >>>>>>>> consistent IO pauses and remove outliers as you mention and as a
>> >>>>
t; I think a JVM change to allow safe points around memory mapped file
>>>>>>>> access is really unlikely although I agree it would be great. I think
>>>>>>>> the best hack around it is to code up your memory mapped file access
>>>>>
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 saf
