[ https://issues.apache.org/jira/browse/HBASE-14190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681063#comment-14681063 ]
Hadoop QA commented on HBASE-14190: ----------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12749715/14190-v7.txt against master branch at commit ae35f65e9ac12256b4514e6ba6ef5333e9e90870. ATTACHMENT ID: 12749715 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 3 new or modified tests. {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0) {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 protoc{color}. The applied patch does not increase the total number of protoc compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:red}-1 checkstyle{color}. The applied patch generated 1865 checkstyle errors (more than the master's current 1862 errors). {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {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:green}+1 site{color}. The mvn post-site goal succeeds with this patch. {color:red}-1 core tests{color}. The patch failed these unit tests: org.apache.hadoop.hbase.security.visibility.TestDefaultScanLabelGeneratorStack org.apache.hadoop.hbase.util.hbck.TestOfflineMetaRebuildBase org.apache.hadoop.hbase.master.TestRestartCluster {color:red}-1 core zombie tests{color}. There are 3 zombie test(s): at org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClient.testCloneSnapshotOfCloned(TestRestoreSnapshotFromClient.java:245) at org.apache.hadoop.hbase.client.TestReplicasClient.testReverseScanWithReplicas(TestReplicasClient.java:612) Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/15034//testReport/ Release Findbugs (version 2.0.3) warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/15034//artifact/patchprocess/newFindbugsWarnings.html Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/15034//artifact/patchprocess/checkstyle-aggregate.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/15034//console This message is automatically generated. > Assign system tables ahead of user region assignment > ---------------------------------------------------- > > Key: HBASE-14190 > URL: https://issues.apache.org/jira/browse/HBASE-14190 > Project: HBase > Issue Type: Bug > Reporter: Ted Yu > Assignee: Ted Yu > Priority: Critical > Attachments: 14190-v6.txt, 14190-v7.txt > > > Currently the namespace table region is assigned like user regions. > I spent several hours working with a customer where master couldn't finish > initialization. > Even though master was restarted quite a few times, it went down with the > following: > {code} > 2015-08-05 17:16:57,530 FATAL [hdpmaster1:60000.activeMasterManager] > master.HMaster: Master server abort: loaded coprocessors are: [] > 2015-08-05 17:16:57,530 FATAL [hdpmaster1:60000.activeMasterManager] > master.HMaster: Unhandled exception. Starting shutdown. > java.io.IOException: Timedout 300000ms waiting for namespace table to be > assigned > at > org.apache.hadoop.hbase.master.TableNamespaceManager.start(TableNamespaceManager.java:104) > at org.apache.hadoop.hbase.master.HMaster.initNamespace(HMaster.java:985) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:779) > at org.apache.hadoop.hbase.master.HMaster.access$500(HMaster.java:182) > at org.apache.hadoop.hbase.master.HMaster$1.run(HMaster.java:1646) > at java.lang.Thread.run(Thread.java:744) > {code} > During previous run(s), namespace table was created, hence leaving an entry > in hbase:meta. > The following if block in TableNamespaceManager#start() was skipped: > {code} > if (!MetaTableAccessor.tableExists(masterServices.getConnection(), > TableName.NAMESPACE_TABLE_NAME)) { > {code} > TableNamespaceManager#start() spins, waiting for namespace region to be > assigned. > There was issue in master assigning user regions. > We tried issuing 'assign' command from hbase shell which didn't work because > of the following check in MasterRpcServices#assignRegion(): > {code} > master.checkInitialized(); > {code} > This scenario can be avoided if we assign hbase:namespace table after > hbase:meta is assigned but before user table region assignment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)