[
https://issues.apache.org/jira/browse/CASSANDRA-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748987#action_12748987
]
Sandeep Tata commented on CASSANDRA-397:
----------------------------------------
Ah ... I think I see now.
Jonathan's assuming that a "fat client" does reads and writes using the
MessagingService but uses thrift to get at the ringcache. (We don't have one of
these in trunk yet.)
Like Jun says, I was assuming that a "fat client" is still talking over thrift
for reads and writes, but uses RingCache to just pick the right node.
> 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.
