[ https://issues.apache.org/jira/browse/HBASE-9696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785433#comment-13785433 ]
Hadoop QA commented on HBASE-9696: ---------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12606604/trunk-9696.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 9 new or modified tests. {color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop 1.0 profile. {color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop 2.0 profile. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:red}-1 findbugs{color}. The patch appears to cause Findbugs (version 1.3.9) to fail. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 lineLengths{color}. The patch does not introduce lines longer than 100 {color:red}-1 site{color}. The patch appears to cause mvn site goal to fail. {color:green}+1 core tests{color}. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/7457//testReport/ Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/7457//console This message is automatically generated. > Master recovery ignores online merge znode > ------------------------------------------ > > Key: HBASE-9696 > URL: https://issues.apache.org/jira/browse/HBASE-9696 > Project: HBase > Issue Type: Bug > Components: master, Region Assignment > Reporter: Jimmy Xiang > Assignee: Jimmy Xiang > Attachments: trunk-9696.patch > > > The online merge znode uses the new region to be created. When master > restarts, the new region is still unknown if the merging is not completed. > Therefore the znode is ignored, which should not. That means the two merging > regions could be moved around. This could cause some data loss if we are not > luck. -- This message was sent by Atlassian JIRA (v6.1#6144)