You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2014/08/19 13:21:19 UTC

[jira] [Commented] (CASSANDRA-7075) Add the ability to automatically distribute your commitlogs across all data volumes

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

Benedict commented on CASSANDRA-7075:
-------------------------------------

[~blambov]: since you're looking at CASSANDRA-6809, it makes sense to address this afterwards, once your fingerprints are on the CL. Worth bearing in mind for your work there.

> 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.2#6252)