[
https://issues.apache.org/jira/browse/HBASE-10401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881777#comment-13881777
]
Hudson commented on HBASE-10401:
--------------------------------
SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-1.1 #63 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-1.1/63/])
HBASE-10401 [hbck] perform overlap group merges in parallel (jmhsieh: rev
1560774)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
> [hbck] perform overlap group merges in parallel
> -----------------------------------------------
>
> Key: HBASE-10401
> URL: https://issues.apache.org/jira/browse/HBASE-10401
> Project: HBase
> Issue Type: Bug
> Components: hbck
> Affects Versions: 0.92.2, 0.98.0, 0.94.16, 0.99.0, 0.96.1.1
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Fix For: 0.98.0, 0.96.2, 0.99.0, 0.94.17
>
> Attachments: hbase-10401.10400.patch, hbase-10401.patch,
> hbase-10401.v2.94.patch, hbase-10401.v2.patch
>
>
> In a recent support case, we encountered a corrupt hbase that had thousands
> of "overlap groups" (regions that had overlapping key ranges). The current
> implementation repairs these by serially taking a group, perorming a merge
> and then moving on to the next group. Because assignments and hdfs nn
> operations are involved each merge could take on the order of seconds. With
> thousands of overlap groups, this could take hours to complete.
> This patch makes it so that these independent merge groups are merged in
> parallel. It uses the same thread pool for other fs info-gathering
> operations.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
