cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Akhil Mehra <>
Subject Re: Don't print Ping caused error logs
Date Mon, 19 Jun 2017 09:44:35 GMT
Just in case you are not aware using a load balancer is an anti patter. Please refer to (

You can turnoff logging for a particular class using the nodetool setlogginglevel (

In your case you can try setting the log level for org.apache.cassandra.transport.Message
to warn using the following command

nodetool setlogginglevel org.apache.cassandra.transport.Message WARN

Obviously this will suppress all info level logging in the message class. 

I hope that helps.


> On 19/06/2017, at 9:13 PM, wrote:
> Hi,
> Our cluster nodes are behind a SLB(Service Load Balancer) with a VIP and the Cassandra
client access the cluster by the VIP. 
> System.log print the below IOException every several seconds. I guess it's the SLB service
which Ping the port 9042 of the Cassandra node periodically and caused the exceptions print.
> Any method to prevend the Ping caused exceptions been print?
> INFO  [SharedPool-Worker-1] 2017-06-19 16:54:15,997 - Unexpected exception
during request; channel = [id: 0x332c09b7, /]
> Error while read(...): Connection reset by peer
> 	at Method) ~[netty-all-4.0.23.Final.jar:4.0.23.Final]
> 	at$EpollSocketUnsafe.doReadBytes(
> 	at$EpollSocketUnsafe.epollInReady(
> 	at ~[netty-all-4.0.23.Final.jar:4.0.23.Final]
> 	at ~[netty-all-4.0.23.Final.jar:4.0.23.Final]
> 	at io.netty.util.concurrent.SingleThreadEventExecutor$
> 	at io.netty.util.concurrent.DefaultThreadFactory$
> 	at [na:1.7.0_85]
> Cheer,
> -Simon

View raw message