[
https://issues.apache.org/jira/browse/HBASE-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017269#comment-13017269
]
stack commented on HBASE-3744:
------------------------------
I think BulkRegionAssigner is not such a good name. BulkAssigner does Regions.
Thats what it does so adding Region to the name doesn't really help.
And i don't think a boolean in the ctor the way to go either. Leave
BulkStartupAssigner as it is. Then make a new class to use in your round
robin table create. I think assignUserRegions should be changed to be
assignAllUserRegions and you should not use this in your createTable method.
Instead you should make a assignTableUserRegions or some such method and in
there, not use BulkStartupAssigner, but your BulkTableAssigner instead.
Something like that.
> 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.92.0
>
> Attachments: 3744.txt, 3744.txt
>
>
> 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
