[
https://issues.apache.org/jira/browse/HBASE-10955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13970530#comment-13970530
]
Hudson commented on HBASE-10955:
--------------------------------
SUCCESS: Integrated in HBase-TRUNK #5088 (See
[https://builds.apache.org/job/HBase-TRUNK/5088/])
HBASE-10955 HBCK leaves the region in masters in-memory RegionStates if region
hdfs dir is lost (enis: rev 1587772)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsckRepair.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsck.java
> HBCK leaves the region in masters in-memory RegionStates if region hdfs dir
> is lost
> -----------------------------------------------------------------------------------
>
> Key: HBASE-10955
> URL: https://issues.apache.org/jira/browse/HBASE-10955
> Project: HBase
> Issue Type: Bug
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 0.99.0
>
> Attachments: hbase-10955.v1.patch
>
>
> One of our tests removes the hdfs directory for the region, and invokes HBCK
> to fix the issue. This test fails flakily because the region is removed from
> meta and unassigned, but the region is not offlined from the masters
> in-memory. This affects further LB runs and disable table, etc.
> In case of {{inMeta && !inHdfs && isDeployed}}, we should not just close the
> region from RS, but call master.unassign().
--
This message was sent by Atlassian JIRA
(v6.2#6252)
