Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 12 Dec 2013 17:52:08 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12684310.1386870447077.25090.1386870728174@arcas>
In-Reply-To: <JIRA.12684310.1386870447077@arcas>
References: <JIRA.12684310.1386870447077@arcas>
Subject: [jira] [Commented] (CASSANDRA-6481) Batchlog endpoint candidates
 should be picked randomly, not sorted by proximity
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-6481:
-------------------------------------------

If dsnitch actually worked then I think this would be fine, but fixing dsnitch is probably out of scope here so +1

> Batchlog endpoint candidates should be picked randomly, not sorted by proximity
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6481
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6481
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Aleksey Yeschenko
>            Assignee: Aleksey Yeschenko
>             Fix For: 1.2.13, 2.0.4
>
>         Attachments: 6481.txt
>
>
> Batchlog endpoint candidates should be picked randomly, not sorted by proximity. I'll be lazy and just copy-paste some lines from IRC:
> [20:23:27] rbranson:	 is there an issue where batch logs tend to get written to a subset of the nodes?
> [20:28:04] rbranson:	 I mean all the write batches are going thru 10% of the nodes
> [20:28:16] rbranson:	 it means writes won't scale linearly w/the cluster size
> Attaching a trivial patch.


--
This message was sent by Atlassian JIRA
(v6.1.4#6159)