cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brosius (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4292) Improve JBOD loadbalancing and reduce contention
Date Wed, 29 Aug 2012 05:40:09 GMT


Dave Brosius commented on CASSANDRA-4292:

Perhaps i am confused, but this commit seems to have screwed up the directory for sstables.

Start with the default configuration (yaml, etc)

- create KS/CF
- add data to CF
- nodetool flush KS - note sstables are in the CF directory
- add more data to same CF
- nodetool flush KS - (a compaction) note sstables are in the top level 'data' directory
> Improve JBOD loadbalancing and reduce contention
> ------------------------------------------------
>                 Key: CASSANDRA-4292
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Yuki Morishita
>             Fix For: 1.2.0 beta 1
>         Attachments: 4292.txt, 4292-v2.txt, 4292-v3.txt, 4292-v4.txt
> As noted in CASSANDRA-809, we have a certain amount of flush (and compaction) threads,
which mix and match disk volumes indiscriminately.  It may be worth creating a tight thread
-> disk affinity, to prevent unnecessary conflict at that level.
> OTOH as SSDs become more prevalent this becomes a non-issue.  Unclear how much pain this
actually causes in practice in the meantime.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message