cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CASSANDRA-8611) give streaming_socket_timeout_in_ms a non-zero default
Date Thu, 20 Aug 2015 18:56:46 GMT

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

Benjamin Lerer reassigned CASSANDRA-8611:
-----------------------------------------

    Assignee: Benjamin Lerer

> give streaming_socket_timeout_in_ms a non-zero default
> ------------------------------------------------------
>
>                 Key: CASSANDRA-8611
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8611
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jeremy Hanna
>            Assignee: Benjamin Lerer
>
> Sometimes as mentioned in CASSANDRA-8472 streams will hang.  We have streaming_socket_timeout_in_ms
which can retry after a timeout.  It would be good to make a default non-zero value.  We don't
want to paper over problems, but streams sometimes hang and you don't want long running streaming
operations to just fail - as in repairs or bootstraps.
> streaming_socket_timeout_in_ms should be based on the tcp idle timeout so it shouldn't
be a problem to set it to on the order of minutes.  Also the socket should only be open during
the actual streaming and not during operations such as merkle tree generation.  We can set
it to a conservative value and people can set it more aggressively as needed.  Disabling as
a default, in my opinion, is too conservative.



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

Mime
View raw message