Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 10 Feb 2016 16:29:18 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12664534.1376954981000.17195.1455121758239@Atlassian.JIRA>
In-Reply-To: <JIRA.12664534.1376954981000@Atlassian.JIRA>
References: <JIRA.12664534.1376954981000@Atlassian.JIRA>
 <JIRA.12664534.1376954981260@arcas>
Subject: [jira] [Commented] (CASSANDRA-5902) Dealing with hints after a
 topology change
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aleksey Yeschenko commented on CASSANDRA-5902:
----------------------------------------------

+1 on the change and overall, thanks. {{HintTest}} is failing though (both on cassci and locally for me). Can you have a look? If not, I will, no problem.

> Dealing with hints after a topology change
> ------------------------------------------
>
>                 Key: CASSANDRA-5902
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5902
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Coordination
>            Reporter: Jonathan Ellis
>            Assignee: Branimir Lambov
>            Priority: Minor
>             Fix For: 3.0.x, 3.x
>
>
> 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)