[
https://issues.apache.org/jira/browse/HBASE-19978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16368719#comment-16368719
]
Duo Zhang commented on HBASE-19978:
-----------------------------------
Oh, we could set the keep alive time to a small value and add an asset at the
end of the test to confirm that the number of workers is back to normal.
> The keepalive logic is incomplete in ProcedureExecutor
> ------------------------------------------------------
>
> Key: HBASE-19978
> URL: https://issues.apache.org/jira/browse/HBASE-19978
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.0.0-beta-2
>
> Attachments: HBASE-19978-v1.patch, HBASE-19978.patch
>
>
> The worker thread will just exit after keep alive time, and we never add it
> back. The only way to add it back is through the stuck checker, this is not
> correct. Here we should start new worker thread if it is under the core pool
> size and there are pending procedures.
> For now the default keep alive time is Long.MAX_VALUE which means no timeout
> so no problem, but we do allow users to set it so we need to fix it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
