hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2405) Close, split, open of regions in RegionServer are run by a single thread only.
Date Tue, 06 Apr 2010 04:38:27 GMT

    [ https://issues.apache.org/jira/browse/HBASE-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853738#action_12853738

stack commented on HBASE-2405:

So worker handles stuff like master ordained OPENs, CLOSEs, QUESCE's as well as SPLITs, COMPACTs,
and FLUSHEs.  The latter are user ordained but are passed out as events by the master.   I
looked at them and SPLITs and COMPACTIONs are just queued. A compaction/split requested is
called on the compactSplitThread.  FLUSH is run inline.

What we want to do here is make it so a long-running close (or open) doesn't hinder other
OPENs, the phenomenon observed by Karthik.  The way around this is to run each open/close
in its own thread.  You cool w/ that JGray?

> 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
>            Assignee: 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.

View raw message