[ https://issues.apache.org/jira/browse/HBASE-20169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439374#comment-16439374 ]
Duo Zhang commented on HBASE-20169: ----------------------------------- But stop is called before join I believe? {code} if (procedureExecutor != null) { configurationManager.deregisterObserver(procedureExecutor.getEnvironment()); procedureExecutor.getEnvironment().getRemoteDispatcher().stop(); procedureExecutor.stop(); procedureExecutor.join(); procedureExecutor = null; } {code} And this method is called in HRegionServer.run so it is not likely to be called twice? It is a bit strange. > NPE when calling HBTU.shutdownMiniCluster (TestAssignmentManagerMetrics is > flakey) > ---------------------------------------------------------------------------------- > > Key: HBASE-20169 > URL: https://issues.apache.org/jira/browse/HBASE-20169 > Project: HBase > Issue Type: Bug > Components: test > Reporter: Duo Zhang > Assignee: stack > Priority: Major > Attachments: HBASE-20169.branch-2.001.patch, > HBASE-20169.branch-2.002.patch, HBASE-20169.branch-2.003.patch, > HBASE-20169.branch-2.004.patch, HBASE-20169.branch-2.005.patch, > HBASE-20169.v0.addendum.patch > > > This usually happens when some master or rs has already been down before we > calling shutdownMiniCluster. > See > https://builds.apache.org/job/HBASE-Flaky-Tests/27223/testReport/junit/org.apache.hadoop.hbase.master/TestAssignmentManagerMetrics/org_apache_hadoop_hbase_master_TestAssignmentManagerMetrics/ > and also > http://104.198.223.121:8080/job/HBASE-Flaky-Tests/34873/testReport/junit/org.apache.hadoop.hbase.master/TestRestartCluster/testRetainAssignmentOnRestart/ > {noformat} > java.lang.NullPointerException > at > org.apache.hadoop.hbase.master.TestAssignmentManagerMetrics.after(TestAssignmentManagerMetrics.java:100) > java.lang.NullPointerException > at > org.apache.hadoop.hbase.master.TestRestartCluster.testRetainAssignmentOnRestart(TestRestartCluster.java:156) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)