[
https://issues.apache.org/jira/browse/CASSANDRA-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473295#comment-13473295
]
Alexey Zotov commented on CASSANDRA-4769:
-----------------------------------------
Yes, I know it. Each DC manages full range of keys. Each key should be written
to some node (in case of RF is 1) in each DC. So there is some node that
responsible for key K in each DC. If node (that responsible fok key K) is down
in one DC, nodes from other DCs should store hint for that node.
So at least one node (in case of RF 1) in each DC will send hints to the node
that has been repaired. That's why I'm talking about DCs instead of nodes.
In case of RF = N each DC will send hints from N nodes.
> Prevent parallel hint delivery to the node
> -------------------------------------------
>
> Key: CASSANDRA-4769
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4769
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.1.2
> Reporter: Alexey Zotov
>
> It's actual only in case of the using a big enough cluster. After node's
> failure other nodes try to send hints to the restored node. So theoretically
> it can affect performance of restored node.
> I suggest to create some mechanism for synchronization of hints delivery
> processes to restored node.
> Could you please explain how it can be implemented.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
