[
https://issues.apache.org/jira/browse/HBASE-22596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reid Chan updated HBASE-22596:
------------------------------
Release Note:
hbase.regionserver.compaction.check.period is used for controlling how often
the compaction checker runs. If unset, will use
hbase.server.thread.wakefrequency as default value.
hbase.regionserver.flush.check.period is used for controlling how ofter the
flush checker runs. If unset, will use hbase.server.thread.wakefrequency as
default value.
> [Chore] Separate the execution period between CompactionChecker and
> PeriodicMemStoreFlusher
> -------------------------------------------------------------------------------------------
>
> Key: HBASE-22596
> URL: https://issues.apache.org/jira/browse/HBASE-22596
> Project: HBase
> Issue Type: Improvement
> Components: Compaction
> Reporter: Reid Chan
> Assignee: Reid Chan
> Priority: Minor
> Attachments: HBASE-22596.master.001.patch
>
>
> The story started at tuning RS performance where I found:
> {code}
> public static final String THREAD_WAKE_FREQUENCY =
> "hbase.server.thread.wakefrequency";
> ...
> this.threadWakeFrequency = conf.getInt(HConstants.THREAD_WAKE_FREQUENCY, 10 *
> 1000);
> ...
> this.compactionChecker = new CompactionChecker(this,
> this.threadWakeFrequency, this);
> this.periodicFlusher = new PeriodicMemStoreFlusher(this.threadWakeFrequency,
> this);
> {code}
> CompactionChecker and PeriodicMemStoreFlusher execution period are bound
> together. (as well as LeaseChecker)
> This issue is going to introduce two new parameters such that user/admin can
> tune them according to business workload.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
