cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8838) Resumable bootstrap streaming
Date Tue, 24 Feb 2015 01:22:14 GMT

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

Yuki Morishita commented on CASSANDRA-8838:
-------------------------------------------

Updated branch with new commit because I found one mistake: https://github.com/yukim/cassandra/tree/8838

IIRC hints are already stored even when bootstrapping node goes down and down time is within
max hint window.
In my opinion, bootstrap streaming failure happens more when streaming source goes down, rather
than bootstrapping node goes down.
When that happens, whole bootstrap process fails in current versions.

I'm working on to prevent whole process failure and instead going to the same state as 'write
survey mode' and nodetool that resume failed streaming from that state.

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

Mime
View raw message