cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8611) give streaming_socket_timeout_in_ms a non-zero default
Date Tue, 25 Aug 2015 07:26:46 GMT


Benjamin Lerer commented on CASSANDRA-8611:

What we are looking for is a safety net, not something too aggressive. Based on the discussion,
I am on favor of setting it to 1 hour. We can still lower it down in the future if needed.
[~rcoli] can you provide another patch for 2.1?

> give streaming_socket_timeout_in_ms a non-zero default
> ------------------------------------------------------
>                 Key: CASSANDRA-8611
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jeremy Hanna
>            Assignee: Benjamin Lerer
>             Fix For: 2.1.x
>         Attachments:
> 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

View raw message