[
https://issues.apache.org/jira/browse/CASSANDRA-7075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351109#comment-15351109
]
Aleksey Yeschenko commented on CASSANDRA-7075:
----------------------------------------------
bq. It's probably not worth pursuing this with the SEDA architecture. Lots of
effort for little gain (now that we have CL compression).
Well, we do have a patch, so we might as well get some benchmark numbers
instead of speculating, before just giving up on this.
bq. But we might need to do CL-segment-per-thread for TPC
Right. Eventually. Not sure how it's relevant here, though.
> 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: Local Write-Read Paths
> Reporter: Tupshin Harper
> Priority: Minor
> Labels: performance
> Fix For: 3.x
>
>
> 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)
