[
https://issues.apache.org/jira/browse/CASSANDRA-7075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144164#comment-14144164
]
Gregory Burd commented on CASSANDRA-7075:
-----------------------------------------
The paper "Aether: A Scalable Approach to Logging"
(http://pandis.net/resources/vldb10aether.pdf) has a great many insights into
how and when an ARIES/WAL can be optimized. I know that's a bit different from
the commitlog/ss-table/memtable used in Cassandra, but there are many ideas
which overlap and might carry over or at least inspire you.
> 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)
