cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-7075) Add the ability to automatically distribute your commitlogs across all data volumes
Date Wed, 23 Apr 2014 14:25:19 GMT

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

Benedict updated CASSANDRA-7075:
--------------------------------

    Description: 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.

> 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
>            Priority: Minor
>              Labels: performance
>
> 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)

Mime
View raw message