[
https://issues.apache.org/jira/browse/HBASE-17912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721127#comment-16721127
]
Hudson commented on HBASE-17912:
--------------------------------
Results for branch branch-1.3
[build #576 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/576/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/576//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/576//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.3/576//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Avoid major compactions on region server startup
> ------------------------------------------------
>
> Key: HBASE-17912
> URL: https://issues.apache.org/jira/browse/HBASE-17912
> Project: HBase
> Issue Type: Improvement
> Components: Compaction
> Affects Versions: 1.3.1, 0.98.24, 2.0.0
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Priority: Major
> Fix For: 1.4.0, 1.3.3, 2.0.0
>
> Attachments: HBASE-17912.patch
>
>
> The HRegionServer.CompactionChecker chore wakes up every 10s and for each
> store in each region mods against a chore frequency (by default slightly
> under 3 hours) to see if it's time to check if a major compaction is
> necessary for that store.
> The check to see if it needs to check for major compactions is calculated by
> if (iteration % multiplier != 0) continue;
> where iteration is the number of times the chore has woken up.
> Because 0 % anything is 0, this will always check for necessary major
> compactions on each store when this chore is first run after the region
> server starts up. This can result in compaction storms when doing a rolling
> restart, because, for example, the new instance of the region server might
> get a lower jitter value than the old one had.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
