You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2016/10/18 21:05:58 UTC

[jira] [Created] (HBASE-16874) Potential NPE from ProcedureExecutor#stop()

Ted Yu created HBASE-16874:
------------------------------

             Summary: Potential NPE from ProcedureExecutor#stop()
                 Key: HBASE-16874
                 URL: https://issues.apache.org/jira/browse/HBASE-16874
             Project: HBase
          Issue Type: Bug
            Reporter: Ted Yu
            Priority: Minor


When examining failed test :
https://builds.apache.org/job/HBase-TRUNK_matrix/lastCompletedBuild/jdk=JDK%201.8%20(latest),label=yahoo-not-h2/testReport/org.apache.hadoop.hbase.master.procedure/TestMasterFailoverWithProcedures/org_apache_hadoop_hbase_master_procedure_TestMasterFailoverWithProcedures/

I noticed the following:
{code}
2016-10-18 18:47:39,313 INFO  [Time-limited test] procedure.TestMasterFailoverWithProcedures(306): Restart 2 exec state: TRUNCATE_TABLE_CLEAR_FS_LAYOUT
Exception in thread "ProcedureExecutorWorker-1" java.lang.NullPointerException
	at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.stop(ProcedureExecutor.java:533)
	at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1197)
	at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:959)
	at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$700(ProcedureExecutor.java:73)
	at org.apache.hadoop.hbase.procedure2.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:1405)
{code}
This seems to be the result of race between stop() and join() methods.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)