[
https://issues.apache.org/jira/browse/CASSANDRA-9895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643363#comment-14643363
]
T Jake Luciani edited comment on CASSANDRA-9895 at 7/27/15 8:55 PM:
--------------------------------------------------------------------
Fix here
https://github.com/tjake/cassandra/commit/bdde214a7e7347461ff20909e52c4aa1b482ac02
was (Author: tjake):
Fix here
https://github.com/tjake/cassandra/commit/61dc411572f1c0b9ed2ebe20015ad523e43c6e98
> 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, 3.0 alpha 1
>
>
> 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)
