A quick search shows SLES 15 provides Java 11 (java-11-openjdk), which is
just fine for Cassandra 4.x.
On Wed, Mar 8, 2023 at 2:56 PM Eric Ferrenbach <
eric.ferrenb...@milliporesigma.com> wrote:
> We are running Cassandra 4.0.7.
>
> We are preparing to migrate our nodes from Centos to SUSE
A few weeks ago, we rolled out TLS among hosts in our clusters (running
4.0.7). More recently we also rolled out TLS between Cassandra clients and
the cluster. Today, we started seeing a lot of dropped actions in one
cluster that correlate with warnings like this:
WARN
Update to this: per https://github.com/openssl/openssl/issues/8068 it
looks like BoringSSL should avoid this issue, so it may be related to
client behavior of some sort. It's unclear to me from the message whether
it's intra-cluster traffic or client/cluster traffic generating the error.
On
1. Check for Nagle/delayed-ack, but probably nodelay is getting set by the
driver so it shouldn't be a problem.
2. Check for network latency (just regular old ping among hosts, during
traffic)
3. Check your GC metrics and see if garbage collections line up with
outliers. Some tuning can help
