[
https://issues.apache.org/jira/browse/HBASE-22596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868275#comment-16868275
]
Hudson commented on HBASE-22596:
--------------------------------
Results for branch branch-1
[build #906 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/906/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/906//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/906//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/906//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> [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
> Fix For: 3.0.0, 1.5.0, 2.3.0, 2.2.1, 2.1.6, 1.4.11
>
> 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)
