[jira] [Comment Edited] (CASSANDRA-5902) Dealing with hints after a topology change

["Ala' Alkhaldi (JIRA)" <ji...@apache.org>]

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

Ala' Alkhaldi edited comment on CASSANDRA-5902 at 7/25/14 11:30 PM:
--------------------------------------------------------------------

Does [this dtest| https://github.com/alaalkhaldi/cassandra-dtest/commit/e03c1525949bdf9f69a40eb60587db4183e9e666] replicate the scenario in the ticket description ? WDYT [~jbellis]


was (Author: ala.alkhaldi):
Does [this dtest| https://github.com/alaalkhaldi/cassandra-dtest/commit/e03c1525949bdf9f69a40eb60587db4183e9e666] replicate the case in the ticket description ? 

> Dealing with hints after a topology change
> ------------------------------------------
>
>                 Key: CASSANDRA-5902
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5902
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Ala' Alkhaldi
>            Priority: Minor
>
> Hints are stored and delivered by destination node id.  This allows them to survive IP changes in the target, while making "scan all the hints for a given destination" an efficient operation.  However, we do not detect and handle new node assuming responsibility for the hinted row via bootstrap before it can be delivered.
> I think we have to take a performance hit in this case -- we need to deliver such a hint to *all* replicas, since we don't know which is the "new" one.  This happens infrequently enough, however -- requiring first the target node to be down to create the hint, then the hint owner to be down long enough for the target to both recover and stream to a new node -- that this should be okay.



--
This message was sent by Atlassian JIRA
(v6.2#6252)