hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3904) HConnection.isTableAvailable returns true even with not all regions available.
Date Wed, 13 Jul 2011 06:08:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064375#comment-13064375

stack commented on HBASE-3904:

Is this commit good for you Ted?  I see NPEs like this:

 Time elapsed: 12.491 sec  <<< ERROR!
        at org.apache.hadoop.hbase.client.HBaseAdmin$1.processRow(HBaseAdmin.java:348)
        at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:212)

v6 patch messed with processRow.

When I run full suite on trunk I see failures stating with org.apache.hadoop.hbase.client.TestMultipleTimestamps.

If I back out this patch, things work for me again.

> 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
>            Assignee: Ted Yu
>            Priority: Minor
>         Attachments: 3904-v3.txt, 3904-v4.txt, 3904-v5.txt, 3904.txt, 3904_v6.patch,
> 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


View raw message