It was the driver after all. The C# driver (and I'm guessing others) query this
table as part of their heartbeat for idle connections. We have a lot of
clients. This adds up.
I don't believe this is the cause of the increasing network traffic.
On Wednesday, April 6, 2016 2:22 PM, Sotirios
Hey,
I'm investigating an issue where the network traffic on a Cassandra 2.1 node
increases over time, regardless of the load our clients are under.
I tried enabling TRACE logging for org.apache.cassandra.transport.Message and
got bombarded with logs like these
DEBUG [SharedPool-Worker-2]
