[
https://issues.apache.org/jira/browse/HBASE-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036959#comment-13036959
]
Ted Yu commented on HBASE-3904:
-------------------------------
My proposal is based on the observation that Vidhyashankar (and other users)
used a loop to check for table availability.
This is equivalent to calling the newly introduced createTableSync() method
where there is no need to write the loop above.
bq. Hence there might be a case when all regions are indeed fully assigned in
META but it is just that the master is yet to populate META with the rest of
the regions.
What Vidhyashankar meant was that the existing entries for the table in .META.
carried server information, but there were more regions to be assigned by
Master which weren't in .META. yet.
> HConnection.isTableAvailable returns true even with not all regions available.
> ------------------------------------------------------------------------------
>
> Key: HBASE-3904
> URL: https://issues.apache.org/jira/browse/HBASE-3904
> Project: HBase
> Issue Type: Bug
> Components: client
> Reporter: Vidhyashankar Venkataraman
> Priority: Minor
>
> This function as per the java doc is supposed to return true iff "all the
> regions in the table are available". But if the table is still being created
> this function may return inconsistent results (For example, when a table with
> a large number of split keys is created).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
