[jira] [Commented] (CASSANDRA-7612) java.io.IOException: Connection reset by peer
[ https://issues.apache.org/jira/browse/CASSANDRA-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073437#comment-14073437 ] Michael Shuler commented on CASSANDRA-7612: --- Is there a particular way to reproduce this error? Is it between nodes in the same datacenter or over the network between data centers? Is there something interesting that happens around this time, or do the nodes recover and keep running fine? Networks are flaky. Connection reset by peer is common among all applications that actually communicate over a network - how they deal with the dropped connection, and subsequently reconnect to continue on working - that's the key. Cassandra should do the right thing here - does it? java.io.IOException: Connection reset by peer - Key: CASSANDRA-7612 URL: https://issues.apache.org/jira/browse/CASSANDRA-7612 Project: Cassandra Issue Type: Bug Reporter: Julien Anguenot Priority: Minor Attachments: cassandra_ioexception_209.txt Exception thrown by all nodes in a multi-DC 2.0.9 cluster on a regular basis. (2 or 3 times a day) Let me know if I can provide more information. Thank you. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CASSANDRA-7612) java.io.IOException: Connection reset by peer
[ https://issues.apache.org/jira/browse/CASSANDRA-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073481#comment-14073481 ] Julien Anguenot commented on CASSANDRA-7612: I actually just found what is causing this reading your comment about the network issue: when a DataStax cluster session at the app level is killed ungracefully it is indeed throwing this error Cassandra side and it makes total sense. I should have thought about that earlier. We just migrated our application from Astyanax to the DataStax CQL Java driver (at the same time as upgrading to 2.0.9) and we did not use to have this stack trace showing up in our monitoring logs when our CI builders were kicking in throughout the day re-deploying our application nodes. Sorry about the noise and thank you very much for your answer. Closing this. java.io.IOException: Connection reset by peer - Key: CASSANDRA-7612 URL: https://issues.apache.org/jira/browse/CASSANDRA-7612 Project: Cassandra Issue Type: Bug Reporter: Julien Anguenot Priority: Minor Attachments: cassandra_ioexception_209.txt Exception thrown by all nodes in a multi-DC 2.0.9 cluster on a regular basis. (2 or 3 times a day) Let me know if I can provide more information. Thank you. -- This message was sent by Atlassian JIRA (v6.2#6252)