[
https://issues.apache.org/jira/browse/CASSANDRA-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748913#action_12748913
]
Sandeep Tata commented on CASSANDRA-397:
----------------------------------------
The echo-ing of writes happens whether you're the bootstrap coordinator or just
another node in the ring (getStorageEndPointsForWrite fix in 375). The only
requirement is that the node doing the write has discovered the bootstrapping
node. Since this fact is advertised on gossip, all nodes know who is
bootstrapping.
(Writes that sneak in before the node has discovered the bootstrapping node
will not be sent, but such is life when we have eventual consistency.)
> 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.
