You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alex Tang (JIRA)" <ji...@apache.org> on 2012/12/21 00:07:13 UTC
[jira] [Commented] (CASSANDRA-4316) Compaction Throttle too bursty
with large rows
[ https://issues.apache.org/jira/browse/CASSANDRA-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537464#comment-13537464 ]
Alex Tang commented on CASSANDRA-4316:
--------------------------------------
This bug is marked as fixed in 1.2.1, however I don't see any fixes being applied in the current trunk (as of 2012-12-20) for this bug. Also, the code that the OP put into the issue (CompactionIterable:116) doesn't seem to have been implemented either. Can someone explain how this was fixed?
Thanks.
> Compaction Throttle too bursty with large rows
> ----------------------------------------------
>
> Key: CASSANDRA-4316
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4316
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.8.0
> Reporter: Wayne Lewis
> Assignee: Yuki Morishita
> Fix For: 1.2.1
>
>
> In org.apache.cassandra.db.compaction.CompactionIterable the check for compaction throttling occurs once every 1000 rows. In our workload this is much too large as we have many large rows (16 - 100 MB).
> With a 100 MB row, about 100 GB is read (and possibly written) before the compaction throttle sleeps. This causes bursts of essentially unthrottled compaction IO followed by a long sleep which yields inconsistence performance and high error rates during the bursts.
> We applied a workaround to check throttle every row which solved our performance and error issues:
> line 116 in org.apache.cassandra.db.compaction.CompactionIterable:
> if ((row++ % 1000) == 0)
> replaced with
> if ((row++ % 1) == 0)
> I think the better solution is to calculate how often throttle should be checked based on the throttle rate to apply sleeps more consistently. E.g. if 16MB/sec is the limit then check for sleep after every 16MB is read so sleeps are spaced out about every second.
--
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: http://www.atlassian.com/software/jira