hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17912) Avoid major compactions on region server startup
Date Sun, 30 Apr 2017 22:24:06 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990442#comment-15990442

Hudson commented on HBASE-17912:

ABORTED: Integrated in Jenkins build HBase-HBASE-14614 #190 (See [https://builds.apache.org/job/HBase-HBASE-14614/190/])
HBASE-17912 - Avoid major compactions on region server startup (tedyu: rev 5eda5fb9d7d7fd5ae77d862c2e1666787e72ead0)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java

> 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: 2.0.0, 1.3.1, 0.98.24
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>             Fix For: 2.0.0, 1.4.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

View raw message