You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2010/04/06 02:22:28 UTC

[jira] Updated: (HBASE-2405) Close, split, open of regions in RegionServer are run by a single thread only.

     [ https://issues.apache.org/jira/browse/HBASE-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-2405:
-------------------------

    Attachment: nsre.txt

I'm going to put up two executor pools -- one with a single thread to do the old QUIESCE, SPLIT, and COMPACTs and then another pool with perhaps 4 or 5 threads to do concurrent OPEN and CLOSEs.

Attached patch cleans up the ugly NSRE thread dump in the RS log.  Will roll that into this patch.

> 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
>
>         Attachments: nsre.txt
>
>
> 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.