cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Boudreault (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-7386) JBOD threshold to prevent unbalanced disk utilization
Date Thu, 20 Nov 2014 16:54:35 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219577#comment-14219577
] 

Alan Boudreault edited comment on CASSANDRA-7386 at 11/20/14 4:54 PM:
----------------------------------------------------------------------

[~snazy] From what I understand, the whole compaction process crashed as soon as it hit 1
disk full. So, no more compaction was happening then. This makes sense since that in my prior
tests, I just make the compaction process very very slow, so nothing was crashing.  [~jjordan]
can confirm if I'm right here.

[~yukim] Will this be backported in branch cassandra-2.0? Thanks 


was (Author: aboudreault):
[~snazy] From what I understand, the whole compaction process crashed as soon as it hit 1
disk full. So, no more compaction was happening then. This makes sense since that in my prior
tests, I just make the compaction process very very slow, so nothing was crashing.  

[~yukim] Will this be backported in branch cassandra-2.0? Thanks 

> JBOD threshold to prevent unbalanced disk utilization
> -----------------------------------------------------
>
>                 Key: CASSANDRA-7386
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7386
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Chris Lohfink
>            Assignee: Robert Stupp
>            Priority: Minor
>             Fix For: 2.1.3
>
>         Attachments: 7386-2.0-v3.txt, 7386-2.0-v4.txt, 7386-2.0-v5.txt, 7386-2.1-v3.txt,
7386-2.1-v4.txt, 7386-2.1-v5.txt, 7386-v1.patch, 7386v2.diff, Mappe1.ods, mean-writevalue-7disks.png,
patch_2_1_branch_proto.diff, sstable-count-second-run.png, test1_no_patch.jpg, test1_with_patch.jpg,
test2_no_patch.jpg, test2_with_patch.jpg, test3_no_patch.jpg, test3_with_patch.jpg, test_regression_no_patch.jpg,
test_regression_with_patch.jpg
>
>
> Currently the pick the disks are picked first by number of current tasks, then by free
space.  This helps with performance but can lead to large differences in utilization in some
(unlikely but possible) scenarios.  Ive seen 55% to 10% and heard reports of 90% to 10% on
IRC.  With both LCS and STCS (although my suspicion is that STCS makes it worse since harder
to be balanced).
> I purpose the algorithm change a little to have some maximum range of utilization where
it will pick by free space over load (acknowledging it can be slower).  So if a disk A is
30% full and disk B is 5% full it will never pick A over B until it balances out.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message