Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <1055207590.1251482672682.JavaMail.jira@brutus>
Date: Fri, 28 Aug 2009 11:04:32 -0700 (PDT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-397) bootstrap and ringcache
In-Reply-To: <121868439.1251476339403.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-397:
------------------------------------------

The point is that RingCache is not aware of TokenMetadata.bootstrapNodes, so fat clients using it cannot ever "discover" bootstrapping nodes.  Rather than making RingCache even more complex now (and again, when we do load balancing / node decommissioning) it seems like making the nodes doing the work is a better encapsulation.

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