[
https://issues.apache.org/jira/browse/CASSANDRA-7446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169577#comment-14169577
]
Jason Brown commented on CASSANDRA-7446:
----------------------------------------
Agreed about letting the decommissioning node replay those batchlogs it has,
but why not give if it enough time to do it naturally - that is, wait until
after the data and hints have streamed? I suspect enough time will have elapsed
in the non-trivial case that the batchlogs would have done what they normally
do. Forcing the replay as the last (or one of the very last) steps makes sense,
and gives the coordinator a few extra moments to get the right thing done.
However, and because I'm lazy right now, we need to double check that
coordinator still sends the batchlog delete command while the decom'ing node is
LEAVING (LEFT, of course, is totally different).
> Batchlog should be streamed to a different node on decom
> --------------------------------------------------------
>
> Key: CASSANDRA-7446
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7446
> Project: Cassandra
> Issue Type: Bug
> Reporter: Aleksey Yeschenko
> Assignee: Branimir Lambov
>
> Just like we stream hints on decom, we should also stream the contents of the
> batchlog - even though we do replicate the batch to at least two nodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
