cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8611) give streaming_socket_timeout_in_ms a non-zero default
Date Mon, 24 Aug 2015 13:26:46 GMT


Paulo Motta commented on CASSANDRA-8611:

If we want to be really conservative, how about setitng it to default linux [tcp_keepalive_time|]
of 7200 seconds (two hours)? Given that I have seen streams hang on EC2 for tens of hours
or even days, this should be sufficient to catch the most extreme scenarios, while still allowing
operators to set it to a lower value if they want to. If this is too conservative, maybe we
can set it to 10-30 minutes.

> 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
> 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