cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10198) 3.0 hints should be streamed on decomission
Date Mon, 14 Sep 2015 12:13:45 GMT

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

Marcus Eriksson commented on CASSANDRA-10198:
---------------------------------------------

Force pushed a new version to the same repo

It should address all your comments.

bq. We must deliver all hints before returning
Patch has an upper limit to how many times we retry before failing - do we want to retry forever?

> 3.0 hints should be streamed on decomission
> -------------------------------------------
>
>                 Key: CASSANDRA-10198
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10198
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Aleksey Yeschenko
>            Assignee: Marcus Eriksson
>             Fix For: 3.0.0 rc1
>
>
> CASSANDRA-6230 added all the necessary pieces in the initial release, but streaming itself
didn't make it in time.
> Now that hints are stored in flat files, we cannot just stream hints sstables. Instead
we need to handoff hints files.
> Essentially we need to rewrite {{StorageService::streamHints}} to be CASSANDRA-6230 aware.
> {{HintMessage}} and {{HintVerbHandler}} can already handle hints targeted for other nodes
(see javadoc for both, it's documented reasonably).
> {{HintsDispatcher}} also takes hostId as an argument, and can stream any hints to any
nodes.
> The building blocks are all there - we just need {{StorageService::streamHints}} to pick
the optimal candidate for each file and use {{HintsDispatcher}} to stream the files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message