Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 24 Jul 2015 15:52:05 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12848924.1437753051000.282511.1437753125268@Atlassian.JIRA>
In-Reply-To: <JIRA.12848924.1437753051000@Atlassian.JIRA>
References: <JIRA.12848924.1437753051000@Atlassian.JIRA>
 <JIRA.12848924.1437753051886@arcas>
Subject: [jira] [Assigned] (CASSANDRA-9895) Batchlog RF>1 writes to a single
 node but not itself.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko reassigned CASSANDRA-9895:
--------------------------------------------

    Assignee: Aleksey Yeschenko

> Batchlog RF>1 writes to a single node but not itself.
> -----------------------------------------------------
>
>                 Key: CASSANDRA-9895
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9895
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: T Jake Luciani
>            Assignee: Aleksey Yeschenko
>             Fix For: 2.1.x
>
>
> 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 batchlog.
> The code is here: https://github.com/apache/cassandra/blob/1c80b04be1d47d03bbde888cea960f5ff8a95d58/src/java/org/apache/cassandra/db/BatchlogManager.java#L530


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