No, i didn't backport that one.
Thank you
Sent using https://www.zoho.com/mail/
Forwarded message
From: Kane Wilson
To:
Date: Mon, 01 Mar 2021 03:18:33 +0330
Subject: Re: using zstd cause high memtable switch count
Forwarded message
OS upgrades most often don't have any impact on C*, and you'd likely only
expect trouble on a major upgrade, but this would typically be related to
package installation, rather than any effects on the database itself.
I wouldn't be too worried about going from RHEL7.4 to 7.9, however going to
8 you
Hi All,
I am running Cassandra 3.11.2 on RHEL 7.4. I am planning for an OS upgrade
from RHEL 7.4 to RHEL 7.9/8.x and SLES15. But I could not find any relevant
information on the impact of upgrading an OS.
Could you share any reference or your analysis of these impacts? I would
appreciate it if yo
If anyone has tried it hasn't been publicized. I wouldn't anticipate any
real issues because it's all Java, but given we don't test on ARM you
should definitely test it out before making the switch in prod.
raft.so - Cassandra consulting, support, and managed services
On Sun, Feb 28, 2021 at 7:0
Did you also backport
https://github.com/apache/cassandra/commit/9c1bbf3ac913f9bdf7a0e0922106804af42d2c1e
to still use LZ4 for flushing? I would be curious if this is a side effect
of using zstd for flushing.
raft.so - Cassandra consulting, support, and managed services
On Sun, Feb 28, 2021 at 9
Hi,
I'm using 3.11.2, just add the patch for zstd and changed table compression
from default (LZ4) to zstd with level 1 and chunk 64kb, everything is fine
(disk usage decreased by 40% and CPU usage is almost the same as before), only
the memtable switch count was changed dramatically; with lz
Hey
Does anyone have experience with running cassandra in aws on arm servers?
Currently running on i3 servers and thinking about upgrading, looking at
i3en vs r6gd.
Obviously a lot of considerations here, but trying to understand what's the
verdict on these arm processors running cassandra.
Gil
