You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tupshin Harper (JIRA)" <ji...@apache.org> on 2014/04/23 16:19:17 UTC

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

Tupshin Harper created CASSANDRA-7075:
-----------------------------------------

             Summary: 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
         Environment: given the prevalance of ssds (no need to separate commitlog and data), and improved jbod support, along with [#3578|https://issues.apache.org/jira/browse/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.
            Reporter: Tupshin Harper
            Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.2#6252)