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 2011/04/19 05:54:05 UTC

[jira] [Resolved] (HBASE-3744) createTable blocks until all regions are out of transition

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

stack resolved HBASE-3744.
--------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.92.0)
                   0.90.3
     Hadoop Flags: [Reviewed]

Committed branch and trunk.  Thanks for original patch Ted.  Its been running in our production > a week and we ran over this issue multiple times doing rolling restarts but master stayed up so seems to be basically working.

> 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
>            Priority: Critical
>             Fix For: 0.90.3
>
>         Attachments: 3744-addendum.txt, 3744-v2.txt, 3744-v3.txt, 3744.txt, create_big_tables.rb, create_big_tables.rb, create_big_tables.rb
>
>
> 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