cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Hanna (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-8621) For streaming operations, when a socket is closed/reset, we should retry/reinitiate that stream
Date Wed, 14 Jan 2015 18:11:35 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-8621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jeremy Hanna updated CASSANDRA-8621:
------------------------------------
    Description: 
Currently we have a setting (streaming_socket_timeout_in_ms) that will timeout and retry the
stream operation in the case where tcp is idle for a period of time.  However in the case
where the socket is closed or reset, we do not retry the operation.  This can happen for a
number of reasons, including when a firewall sends a reset message on a socket during a streaming
operation, such as nodetool rebuild necessarily across DCs or repairs.

Doing a retry would make the streaming operations more resilient.  It would be good to log
the retry clearly as well (with the stream session ID).

  was:
Currently we have a setting (streaming_socket_timeout_in_ms) that will timeout and retry the
stream operation in the case where tcp is idle for a period of time.  However in the case
where the socket is closed or reset, we do not retry the operation.  This can happen for a
number of reasons, including when a firewall sends a reset message on a socket during a streaming
operation - think nodetool rebuild necessarily across DCs or repairs.

Doing a retry would make the streaming operations more resilient.  It would be good to log
the retry clearly as well (with the stream session ID).


> For streaming operations, when a socket is closed/reset, we should retry/reinitiate that
stream
> -----------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8621
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8621
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jeremy Hanna
>            Assignee: Yuki Morishita
>
> Currently we have a setting (streaming_socket_timeout_in_ms) that will timeout and retry
the stream operation in the case where tcp is idle for a period of time.  However in the case
where the socket is closed or reset, we do not retry the operation.  This can happen for a
number of reasons, including when a firewall sends a reset message on a socket during a streaming
operation, such as nodetool rebuild necessarily across DCs or repairs.
> Doing a retry would make the streaming operations more resilient.  It would be good to
log the retry clearly as well (with the stream session ID).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message