cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7446) Batchlog should be streamed to a different node on decom
Date Mon, 13 Oct 2014 17:32:34 GMT

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

Aleksey Yeschenko commented on CASSANDRA-7446:
----------------------------------------------

I prefer to not trust anything that's based purely on timeouts. Besides, there are edge cases
when you can't guarantee that it'd be replayed within a short time bound. Say, hypothetically,
if you have a lot to replay, and each page has a very-long, but non timing out, replays. So
I'd do that just to be safe.

bq. 'm lazy right now, we need to double check that coordinator still sends the batchlog delete
command while the decom'ing node is LEAVING 

Why? Even if it doesn't, it's no big deal. Worst case scenario - we replay something twice,
which is harmless, just (very) slightly wasteful.

> 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)

Mime
View raw message