[
https://issues.apache.org/jira/browse/CASSANDRA-10198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14876083#comment-14876083
]
Aleksey Yeschenko commented on CASSANDRA-10198:
-----------------------------------------------
CI results:
[dtest|http://cassci.datastax.com/job/iamaleksey-10198-3.0-dtest/2/testReport/]
and
[testall|http://cassci.datastax.com/view/Dev/view/iamaleksey/job/iamaleksey-10198-3.0-testall/lastCompletedBuild/testReport/]
Committed as
[959b96efee613363fde28de1e2b34aa9201efd7a|https://github.com/apache/cassandra/commit/959b96efee613363fde28de1e2b34aa9201efd7a]
to cassandra-3.0 and merged with trunk.
Thanks.
> 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)
