[
https://issues.apache.org/jira/browse/HBASE-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168185#comment-13168185
]
Hudson commented on HBASE-4881:
-------------------------------
Integrated in HBase-0.92-security #37 (See
[https://builds.apache.org/job/HBase-0.92-security/37/])
HBASE-4881 Unhealthy region is on service caused by rollback of region
splitting; overcommitted in RegionServerMetrics -- reverting change on this file
HBASE-4881 Unhealthy region is on service caused by rollback of region splitting
stack :
Files :
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/metrics/RegionServerMetrics.java
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/SplitTransaction.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/metrics/RegionServerMetrics.java
> Unhealthy region is on service caused by rollback of region splitting
> ---------------------------------------------------------------------
>
> Key: HBASE-4881
> URL: https://issues.apache.org/jira/browse/HBASE-4881
> Project: HBase
> Issue Type: Bug
> Reporter: chunhui shen
> Assignee: chunhui shen
> Fix For: 0.92.0
>
> Attachments: 4881-v2.txt, hbase-4881.patch
>
>
> If region splitting is failed in the state of
> JournalEntry.CLOSED_PARENT_REGION
> It will be rollback as the following steps:
> {code}
> 1.case CLOSED_PARENT_REGION:
> this.parent.initialize();
> break;
> 2.case CREATE_SPLIT_DIR:
> this.parent.writestate.writesEnabled = true;
> cleanupSplitDir(fs, this.splitdir);
> break;
> 3.case SET_SPLITTING_IN_ZK:
> if (server != null && server.getZooKeeper() != null) {
> cleanZK(server, this.parent.getRegionInfo());
> }
> break;
> {code}
> If this.parent.initialize() throws IOException in step 1,
> If check filesystem is ok. it will do nothing.
> However, the parent region is on service now.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
