You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Reid Chan (JIRA)" <ji...@apache.org> on 2019/06/17 05:11:00 UTC
[jira] [Created] (HBASE-22596) [Chore] Separate the execution
period between CompactionChecker and PeriodicMemStoreFlusher
Reid Chan created HBASE-22596:
---------------------------------
Summary: [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
Reporter: Reid Chan
Assignee: Reid Chan
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)