cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9895) Batchlog RF>1 writes to a single node but not itself.
Date Wed, 29 Jul 2015 15:44:04 GMT


Aleksey Yeschenko commented on CASSANDRA-9895:

I'm not sure if CASSANDRA-6551 broke it, or if it's been like this forever, or if it was something
else, but there is a bug at the moment.

We are *not* throwing UAE if we have less than 2 replicas for the batch. The attached patch
shows what the intended behaviour should be, as I see it.

> Batchlog RF>1 writes to a single node but not itself.
> -----------------------------------------------------
>                 Key: CASSANDRA-9895
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: T Jake Luciani
>             Fix For: 2.1.x, 3.0 beta 1
>         Attachments: 9895.txt
> In the batchlogmanager when selecting the endpoints for to write the batchlog to, for
RF>1,  we filter out any down nodes and the local node. 
> This means we require two nodes up but only write to one.  Why? This affects availability
since we need two nodes to write at CL.ONE.  
> If we *require* two copies of the batchlog then we should include ourselfs in the calculation.
> If we allow a batchlog write with only a single node up then we should write to the local
> The code is here:

This message was sent by Atlassian JIRA

View raw message