cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandeep Tata (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-213) complete bootstrap code
Date Tue, 28 Jul 2009 06:12:16 GMT

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

Sandeep Tata commented on CASSANDRA-213:
----------------------------------------

Ah, that makes sense.

I was confused by "Eventually we want the old node to keep serving requests until the new
node has the data."  meant. I guess you're talking about extra coordination to make sure a
new node doesn't start serving reads until it gets the data from all its bootstrap buddies.

> complete bootstrap code
> -----------------------
>
>                 Key: CASSANDRA-213
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-213
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Sandeep Tata
>            Priority: Critical
>             Fix For: 0.4
>
>
> The bootstrap code sends files from DatabaseDescriptor.getBootstrapFileLocation to the
node that is joining the ring, but nothing actually puts files into that directory.
> There are probably other bugs / omissions we will find as we flesh this out.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message