[
https://issues.apache.org/jira/browse/HBASE-14969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202707#comment-15202707
]
Yu Li commented on HBASE-14969:
-------------------------------
bq. This change switches the default compaction throughput controller to
PressureAwareCompactionThroughputController in 1.3, which limits throughput to
an upper bound of 20MB by default
Checking the commit and it seemed to me the default compaction throughput
controller is still the no limit one, excerpt from
{{CompactionThroughputControllerFactory}}:
{code}
private static final Class<? extends ThroughputController>
DEFAULT_THROUGHPUT_CONTROLLER_CLASS = NoLimitThroughputController.class;
{code}
Mind give it a double check sir [~ghelmling]? Thanks.
On the other hand, since this is kind of a new feature and did some refactor,
yes let me prepare one release note.
> Add throughput controller for flush
> -----------------------------------
>
> Key: HBASE-14969
> URL: https://issues.apache.org/jira/browse/HBASE-14969
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 2.0.0, 1.3.0
> Reporter: Yu Li
> Assignee: Yu Li
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-14969-addendum-branch-1.patch,
> HBASE-14969.branch-1.patch, HBASE-14969.patch, HBASE-14969_v10.patch,
> HBASE-14969_v2.patch, HBASE-14969_v3.patch, HBASE-14969_v4.patch,
> HBASE-14969_v5.patch, HBASE-14969_v6.patch, HBASE-14969_v9.patch,
> fd78628_9909808_compat_report.html, load-nothrottling.log, load-throttling.log
>
>
> In HBASE-8329 we added a throughput controller for compaction, to avoid spike
> caused by huge IO pressure like network/disk overflow. However, even with
> this control on, we are still observing disk utils near 100%, and by analysis
> we think this is caused by flush, especially when we increase the setting of
> {{hbase.hstore.flusher.count}}
> In this JIRA, we propose to add throughput control feature for flush, as a
> supplement of HBASE-8329 to better control IO pressure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
