Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 881171868D for ; Thu, 20 Aug 2015 18:56:46 +0000 (UTC) Received: (qmail 98489 invoked by uid 500); 20 Aug 2015 18:56:46 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 98458 invoked by uid 500); 20 Aug 2015 18:56:46 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 98443 invoked by uid 99); 20 Aug 2015 18:56:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Aug 2015 18:56:46 +0000 Date: Thu, 20 Aug 2015 18:56:46 +0000 (UTC) From: "Benjamin Lerer (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (CASSANDRA-8611) give streaming_socket_timeout_in_ms a non-zero default MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)