You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/05/01 22:24:00 UTC

[jira] [Created] (HBASE-20515) Cleanup ProcedureExecutor#stop and #join interaction/dependency

stack created HBASE-20515:
-----------------------------

             Summary: Cleanup ProcedureExecutor#stop and #join interaction/dependency
                 Key: HBASE-20515
                 URL: https://issues.apache.org/jira/browse/HBASE-20515
             Project: HBase
          Issue Type: Task
          Components: amv2
            Reporter: stack


See HBASE-20169 discussion toward the end. What the discussion makes clear is that there is an ordering expected around the shutdown of PerformanceExecutor; first #stop must be called and then #join. In multi-threaded context, this may not always happen.

Also look at #join. It is doing harvesting and cleanup which is not what a #join usually does; #join is usually more an observer than a final tidying of resources.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)