[HBASE-22596] [Chore] Separate the execution period between CompactionChecker and PeriodicMemStoreFlusher

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha-1, 1.5.0, 2.3.0, 2.2.1, 2.1.6, 1.4.11
• Component/s: Compaction
• Hadoop Flags: Reviewed

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.

• Assignee: Reid Chan
• Reporter: Reid Chan
• Created: 17/Jun/19 05:10
• Updated: 20/Jun/19 08:25
• Resolved: 20/Jun/19 03:22

Description

The story started at tuning RS performance where I found:

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);

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.

Issue Links

• supercedes: HBASE-22609 [Docs] More detail documentation about "hbase.server.thread.wakefrequency"
• links to: GitHub Pull Request #319
• links to: GitHub Pull Request #319