Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 6 Mar 2015 16:39:39 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12710049.1398262670000.21796.1425659979202@Atlassian.JIRA>
In-Reply-To: <JIRA.12710049.1398262670000@Atlassian.JIRA>
References: <JIRA.12710049.1398262670000@Atlassian.JIRA>
 <JIRA.12710049.1398262670110@arcas>
Subject: [jira] [Updated] (CASSANDRA-7075) Add the ability to automatically
 distribute your commitlogs across all data volumes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis updated CASSANDRA-7075:
--------------------------------------
    Reviewer: Benedict

[~benedict] to review

> Add the ability to automatically distribute your commitlogs across all data volumes
> -----------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7075
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7075
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Tupshin Harper
>            Assignee: Branimir Lambov
>            Priority: Minor
>              Labels: performance
>             Fix For: 3.0
>
>
> given the prevalance of ssds (no need to separate commitlog and data), and improved jbod support, along with CASSANDRA-3578, it seems like we should have an option to have one commitlog per data volume, to even the load. i've been seeing more and more cases where there isn't an obvious "extra" volume to put the commitlog on, and sticking it on only one of the jbodded ssd volumes leads to IO imbalance.


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