Hello Annuj,, I checked my settings and this what I got. root@node001[SPH][BENCH][PnS3]:~$ sysctl -A | grep net.ipv4 | grep net.ipv4.tcp_keepalive_probes net.ipv4.tcp_keepalive_probes = 9 root@node001[SPH][BENCH][PnS3]:~$ sysctl -A | grep net.ipv4 | grep net.ipv4.tcp_keepalive_intvl net.ipv4.tcp_keepalive_intvl = 75 root@node001[SPH][BENCH][PnS3]:~$ sysctl -A | grep net.ipv4 | grep net.ipv4.tcp_keepalive_time net.ipv4.tcp_keepalive_time = 300The tcp_keepalive_time is quite high in comparation to that written on the doc https://docs.datastax.com/en/cassandra/2.1/cassandra/troubleshooting/trblshootIdleFirewall.html Do you think that is ok? Best regards
Jean Carlo "The best way to predict the future is to invent it" Alan Kay On Fri, Jan 29, 2016 at 11:02 AM, Anuj Wadehra <anujw_2...@yahoo.co.in> wrote: > Hi Jean, > > Please make sure that your Firewall is not dropping TCP connections which > are in use. Tcp keep alive on all nodes must be less than the firewall > setting. Please refer to > > https://docs.datastax.com/en/cassandra/2.0/cassandra/troubleshooting/trblshootIdleFirewall.html > for > details on TCP settings. > > > Thanks > Anuj > > Sent from Yahoo Mail on Android > <https://overview.mail.yahoo.com/mobile/?.src=Android> > > On Fri, 29 Jan, 2016 at 3:21 pm, Jean Carlo > <jean.jeancar...@gmail.com> wrote: > Hello guys, > > I have a cluster cassandra 2.1.12 with 6 nodes. All the logs of my nodes > are having this messages marked as INFO > > INFO [SharedPool-Worker-1] 2016-01-29 10:40:57,745 Message.java:532 - > Unexpected exception during request; channel = [id: 0xff15eb8c, / > 172.16.162.4:9042] > java.io.IOException: Error while read(...): Connection reset by peer > at io.netty.channel.epoll.Native.readAddress(Native Method) > ~[netty-all-4.0.23.Final.jar:4.0.23.Final] > at > io.netty.channel.epoll.EpollSocketChannel$EpollSocketUnsafe.doReadBytes(EpollSocketChannel.java:675) > ~[netty-all-4.0.23.Final.jar:4.0.23.Final] > at > io.netty.channel.epoll.EpollSocketChannel$EpollSocketUnsafe.epollInReady(EpollSocketChannel.java:714) > ~[netty-all-4.0.23.Final.jar:4.0.23.Final] > at > io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:326) > ~[netty-all-4.0.23.Final.jar:4.0.23.Final] > at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:264) > ~[netty-all-4.0.23.Final.jar:4.0.23.Final] > at > io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) > ~[netty-all-4.0.23.Final.jar:4.0.23.Final] > at > io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) > ~[netty-all-4.0.23.Final.jar:4.0.23.Final] > at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60] > > This happens either the cluster is stressed or not. Btw it is not > production. The ip marked there (172.16.162.4) belongs to a node of the > cluster, this is not the only node that appears, acctually we are having > all the node's ip having that reset by peer problem. > > Our cluster is having more reads than writes. like 50 reads per second. > > Any one got the same problem? > > > Best regards > > Jean Carlo > > "The best way to predict the future is to invent it" Alan Kay > >
