That message gets logged when the node tries to respond back to the client
but the driver has already given up waiting for the cluster to respond so
the connection is no longer active.
It typically happens when running an expensive query and the coordinator is
still waiting for the replicas to res
Hi Renoy,
The message below shows there are connection hick-ups between Remote and
Local machines.
Unexpected exception during request; channel = [id: 0x08a9bc0f, L:/
10.50.11.123:9042 ! R:/10.50.11.182:44734]
L stands for local machine address and R stands for Remote machine address.
Please c
Hi,
We are having a 5 node Cassandra cluster running in version 3.0.13.
Recently we upgrade the Cassandra cpp driver on the application side
from cassandra-cpp-driver-2.6.0-1.el7.centos.x86_64
to cassandra-cpp-driver-2.15.3-1.el7.x86_64. After the upgrade, Cassandra
system.log is continuously fill
