You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sandeep Tata (JIRA)" <ji...@apache.org> on 2009/08/28 19:12:32 UTC

[jira] Commented: (CASSANDRA-397) bootstrap and ringcache

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

Sandeep Tata commented on CASSANDRA-397:
----------------------------------------

Doesn't RingCache just get data from cloneTokenEndPointMap() ?  So fat clients won't see the Bootstrapping node until it finishes. What am I missing?

> bootstrap and ringcache
> -----------------------
>
>                 Key: CASSANDRA-397
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-397
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jonathan Ellis
>             Fix For: 0.5
>
>
> Bootstrap mode makes it easy to shoot yourself in the foot with RingCache (see CASSANDRA-197).
> One solution would be to have the node that is providing data to the new, bootstrapping node, echo writes to the new node.  Currently, the coordinator node is in charge of including the new node as an "extra" replica, but if a fat client is using messagingservice directly with RingCache that doesn't work.

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