You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/12/12 18:52:08 UTC
[jira] [Commented] (CASSANDRA-6481) Batchlog endpoint candidates
should be picked randomly, not sorted by proximity
[ 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)