Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 6 Apr 2011 21:28:05 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <343176019.38809.1302125285822.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <69674369.38684.1302122765765.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (HBASE-3744) createTable blocks until all regions
 are out of transition
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ted Yu reassigned HBASE-3744:
-----------------------------

    Assignee: Ted Yu

> createTable blocks until all regions are out of transition
> ----------------------------------------------------------
>
>                 Key: HBASE-3744
>                 URL: https://issues.apache.org/jira/browse/HBASE-3744
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.90.1
>            Reporter: Todd Lipcon
>            Assignee: Ted Yu
>             Fix For: 0.92.0
>
>
> In HBASE-3305, the behavior of createTable was changed and introduced this bug: createTable now blocks until all regions have been assigned, since it uses BulkStartupAssigner. BulkStartupAssigner.waitUntilDone calls assignmentManager.waitUntilNoRegionsInTransition, which waits across all regions, not just the regions of the table that has just been created.
> We saw an issue where one table had a region which was unable to be opened, so it was stuck in RegionsInTransition permanently (every open was failing). Since this was the case, waitUntilDone would always block indefinitely even though the newly created table had been assigned.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira