[
https://issues.apache.org/jira/browse/HBASE-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037218#comment-13037218
]
Ted Yu commented on HBASE-3904:
-------------------------------
>From Vidhyashankar's test:
{code}
Table test-v6 not yet available... Sleeping for 5 more minutes... Expected
#regions = 17933
Table is probably available!! : test-v6 Available? true
Table test-v6may not be available... Double checking: Sleeping for 5 minutes
more...
Table test-v6: Expected # Regions = 17933 Actual number = 4744
{code}
We can see that after conn.isTableAvailable() returned true, there were still
at least 13189 regions that were not assigned - not reaching .META.
I think we should implement createTableSync() as I proposed earlier.
We can ask user to call table.getRegionsInfo() but that is not convenient, and
getRegionsInfo() is marked deprecated.
> 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
> Attachments: 3904.txt
>
>
> 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
