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 Wed,
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 [epollEventLoopGroup-5-31
