Hello Edi,
Before attempt to prematurely optimise, let's try to understand the
situation a bit better.
* What's the bandwidth available? (think: total bandwidth and the
typical usage)
* What's causing the heavy network load?
* How much bandwidth is consumed by the heavy network load?
* How long do they typically last?
* How frequent does that happen?
* Is the thing causing the load flexible to run at a slower rate or at a
different time of the day/week?
It's usually better to address the problem at source, instead of
tweaking the victims and hoping that they will better survive it.
Cheers,
Bowen
On 27/08/2024 12:57, edi mari wrote:
Hello ,
Recently, we've noticed errors appearing in the Cassandra logs, which
coincide with periods of heavy network load. We investigated and
confirmed that the network was under significant stress during these
times.
Is there any configuration or tuning in Cassandra that could help
eliminate these errors?
Perhaps increasing the inbound connection timeout might help?
Cassandra V4.0.4
ERROR [Messaging-EventLoop-3-6] 2024-08-27 01:31:33,741
InboundMessageHandler.java:300 -
/xx.xx.xx.xx:7000->/xx.xx.xx.xx:7000-SMALL_MESSAGES-fbe3b1a9
unexpected exception caught while processing inbound messages;
terminating connection
ERROR [Messaging-EventLoop-3-4] 2024-08-27 11:10:16,390
InboundMessageHandler.java:300 -
/xx.xx.xx.xx:7000->/xx.xx.xx.xx:7000-SMALL_MESSAGES-5d216061
unexpected exception caught while processing inbound messages;
terminating connection
