Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 20 Feb 2015 20:02:12 +0000 (UTC)
From: "T Jake Luciani (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12776349.1424403548000.97820.1424462532463@Atlassian.JIRA>
In-Reply-To: <JIRA.12776349.1424403548000@Atlassian.JIRA>
References: <JIRA.12776349.1424403548000@Atlassian.JIRA>
 <JIRA.12776349.1424403548990@arcas>
Subject: [jira] [Commented] (CASSANDRA-8838) Resumable bootstrap streaming
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-8838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329459#comment-14329459 ] 

T Jake Luciani commented on CASSANDRA-8838:
-------------------------------------------

This is a major win!  Since failed bootstraps on dense nodes can take many hours.  If anything goes wrong you need to wipe and restart.


> Resumable bootstrap streaming
> -----------------------------
>
>                 Key: CASSANDRA-8838
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8838
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Yuki Morishita
>            Assignee: Yuki Morishita
>            Priority: Minor
>             Fix For: 3.0
>
>         Attachments: 0001-Resumable-bootstrap-streaming.patch
>
>
> This allows the bootstrapping node not to be streamed already received data.
> The bootstrapping node records received keyspace/ranges as one stream session completes. When some sessions with other nodes fail, bootstrapping fails also, though next time it re-bootstraps, already received keyspace/ranges are skipped to be streamed.


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