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

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis commented on CASSANDRA-5902:
-------------------------------------------

You'll want to use CL.ALL instead of ONE when sending to all replicas.

Also, please update to conform with http://wiki.apache.org/cassandra/CodeStyle.

Otherwise LGTM!

(Note: a branch is just as easy to merge as a pull request, so you don't need to create the PR unless it scratches some OCD on your end.)

> 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: Branimir Lambov
>            Priority: Minor
>             Fix For: 2.1.1
>
>
> 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.3.4#6332)