Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 28 Mar 2012 21:07:28 +0000 (UTC)
From: "Brandon Williams (Reopened) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <406085683.30052.1332968848184.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1517832605.16285.1331764719587.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Reopened] (CASSANDRA-4051) Stream sessions can only fail
 via the FailureDetector
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams reopened CASSANDRA-4051:
-----------------------------------------


Reopening because this only fixes the problem in one way, FileStreamTask can still fail all 8 times and never close the session.  In general, outbound streaming's "fire and forget" methodology is problematic for bulk loading.
                
> Stream sessions can only fail via the FailureDetector
> -----------------------------------------------------
>
>                 Key: CASSANDRA-4051
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4051
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>              Labels: streaming
>             Fix For: 1.1.0
>
>         Attachments: 4051-v2.txt, 4051.txt
>
>
> If for some reason, FileStreamTask itself fails more than the number of retry attempts but gossip continues to work, the stream session will never be closed.  This is unlikely to happen in practice since it requires blocking the storage port from new connections but keeping the existing ones, however for the bulk loader this is especially problematic since it doesn't have access to a failure detector and thus no way of knowing if a session failed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira