[ https://issues.apache.org/jira/browse/HBASE-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016577#comment-13016577 ]
Ted Yu commented on HBASE-3744: ------------------------------- >From IRC: tlipcon_: it seems wrong that we use something called BukStartupAssigner in the first place [2:54pm] tlipcon_: since this is not startup ... tlipcon_: i think BulkStartupAssigner should be renamed [3:11pm] tlipcon_: and then either a parameter or a different subclass that doesn't wait > 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 > > Attachments: 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