Hi, Adil, thanks for response.

Both before and after C* upgrade we're using java driver 3.0.3, which seems to be compatible to 2.2.7 and 3.0.8.

Also I forgot to mention that such errors occur even when there are no clients connected to cluster.


2016-10-02 7:57 GMT+00:00 Adil <adil.chabaq@gmail.com>:

Hi,
That means that some clients closes the connection, have you upgraded all clients?


Il 30/set/2016 14:25, "Oleg Krayushkin" <allight.me@gmail.com> ha scritto:

Hi,

Since the upgrade from Cassandra version 2.2.7 to 3.0.8 We're getting following error almost every several minutes on every node. For node at 173.170.147.120 error in system.log would be:

INFO  [SharedPool-Worker-4] 2016-09-30 10:26:39,068 Message.java:605 
   - Unexpected exception during request; channel = [id: 0xfd64cd67, /173.170.147.120:50660 :> /18.4.63.191: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_91]

As far as I see, in all such errors there are always [id: <...>, /<broadcast_address>:<some_port> :> /<listen_address>:<native_transport_port>.  Also broadcast_address and listen_address are always belong to the current node adresses.

What are possible reasons of such errors and how can I fix it? Any thoughts would be appreciated.