You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Shuler (JIRA)" <ji...@apache.org> on 2015/11/16 22:44:10 UTC
[jira] [Commented] (CASSANDRA-10714) tcp retransmission issue seen
in cassandra cluster
[ https://issues.apache.org/jira/browse/CASSANDRA-10714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007390#comment-15007390 ]
Michael Shuler commented on CASSANDRA-10714:
--------------------------------------------
This could be simple network issues with a NIC, switch port, or neighbor, so TCP does its job and retransmits packets. You might see error|dropped|overruns values in ifconfig, as well. If this persists on a particular node in your cluster, it may be prudent to destroy that node and launch another one in the hopes that you get a more stable server.
> tcp retransmission issue seen in cassandra cluster
> --------------------------------------------------
>
> Key: CASSANDRA-10714
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10714
> Project: Cassandra
> Issue Type: Improvement
> Components: Streaming and Messaging
> Reporter: Jeff Liu
>
> I have been seen tcp package retransmission issue in various stacks in our environment. ( AWS with no VPC). I'm currently using hsha rpc server type on cassandra 2.1.6 version. The information captured by wireshark shows that the retransmission happened both between client-to-server and server-to-server. Even within a cluster that doesn't have any client traffic, sporadic retransmission still happens.
> It's pretty easy to reproduce this issue by watching "netstat -s | grep retrans".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)