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-397) bootstrap and ringcache
Date Fri, 28 Aug 2009 21:37:33 GMT

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

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

>> "extra" replica, but if a fat client is using messagingservice directly with RingCache
that doesn't work.

Ugh .. right in the description :-| As I said, makes sense now.

Perhaps we can worry about this once we actually have fat clients that use messaging service
As jbellis said in CASSANDRA-197, I'd assume this kind of fat client should probably participate
in gossip without grabbing a token so it doesn't have to deal with RingCache over thrift.

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


Mime
View raw message