[
https://issues.apache.org/jira/browse/HBASE-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852990#action_12852990
]
Jonathan Gray commented on HBASE-2405:
--------------------------------------
The way we prevent blocking is by not doing anything long-running in the thread
that processes messages. If it's a close, he can asynchronously trigger the
close to happen (into compaction queue w/ a callback perhaps).
Or we have a process thread that handles all incoming messages, decides what to
do and hands that off to a set of workers or something. Anyways, I'm not
against adding worker pools just want to think about all possible designs.
> Close, split, open of regions in RegionServer are run by a single thread only.
> ------------------------------------------------------------------------------
>
> Key: HBASE-2405
> URL: https://issues.apache.org/jira/browse/HBASE-2405
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.20.4, 0.21.0
>
>
> JGray and Karthik observed yesterday that a regoin open message arrived at
> the regionserver but that the regionserver worker thread did not get around
> to the actually opening until 45 seconds later (region offline for 45
> seconds). We only run a single Worker thread in a regoinserver processing
> open, close, and splits. In this case, a long running close (or two) held up
> the worker thread. We need to run more than a single worker. A pool of
> workers? Should opens be prioritized?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
