[
https://issues.apache.org/jira/browse/HBASE-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037005#comment-13037005
]
stack commented on HBASE-3904:
------------------------------
bq. 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.
I'm not sure how this is possible but I may not have done sufficient study.
bq. Server info was initially omitted.
Yes, thats how it works. Later, on assignment, the server gets filled in.
On your patch:
{code}
+ if (!(info.isOffline() || info.isSplit())) {
+ regionCount.incrementAndGet();
+ }
{code}
This is good Ted.
This is good too --> '+ MetaScanner.metaScan(conf, visitor, tableName);'
Vidhya, do you want to try Ted's patch? Its client-side only patch.
@Ted A unit test would be nice.
> 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
