hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-495) No server address listed in .META.
Date Fri, 07 Mar 2008 21:29:46 GMT

     [ https://issues.apache.org/jira/browse/HBASE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack updated HBASE-495:
------------------------

    Attachment: 495-v2-0.16.0.patch

Version 2 of 495 patch for 0.16.0; this one actually passes tests.

> No server address listed in .META.
> ----------------------------------
>
>                 Key: HBASE-495
>                 URL: https://issues.apache.org/jira/browse/HBASE-495
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.16.0
>            Reporter: stack
>             Fix For: 0.1.0, 0.2.0
>
>         Attachments: 495-0.1.patch, 495-0.16.0.patch, 495-v2-0.16.0.patch
>
>
> Michael Bieniosek manufactured the following in a 0.16.0 install:
> {code}
> 08/03/06 17:52:02 DEBUG hbase.HTable: Advancing internal scanner to startKey g80Fi5WZHlzLqGzErrAd7V==
> 08/03/06 17:52:02 DEBUG hbase.HConnectionManager$TableServers: reloading table servers
because: No server address listed in .META. for region enwiki_080103,g80Fi5WZHlzLqGzErrAd7V==,1204768636421
> 08/03/06 17:52:12 DEBUG hbase.HConnectionManager$TableServers: reloading table servers
because: No server address listed in .META. for region enwiki_080103,g80Fi5WZHlzLqGzErrAd7V==,1204768636421
> 08/03/06 17:52:22 DEBUG hbase.HConnectionManager$TableServers: reloading table servers
because: No server address listed in .META. for region enwiki_080103,g80Fi5WZHlzLqGzErrAd7V==,1204768636421
> org.apache.hadoop.hbase.NoServerForRegionException: No server address listed in .META.
for region enwiki_080103,g80Fi5WZHlzLqGzErrAd7V==,1204768636421
>         at org.apache.hadoop.hbase.HConnectionManager$TableServers.locateRegionInMeta(HConnectionManager.java:449)
>         at org.apache.hadoop.hbase.HConnectionManager$TableServers.locateRegion(HConnectionManager.java:346)
>         at org.apache.hadoop.hbase.HConnectionManager$TableServers.locateRegion(HConnectionManager.java:309)
>         at org.apache.hadoop.hbase.HTable.getRegionLocation(HTable.java:103)
>         at org.apache.hadoop.hbase.HTable$ClientScanner.nextScanner(HTable.java:854)
>         at org.apache.hadoop.hbase.HTable$ClientScanner.next(HTable.java:915)
>         at org.apache.hadoop.hbase.hql.SelectCommand.scanPrint(SelectCommand.java:233)
>         at org.apache.hadoop.hbase.hql.SelectCommand.execute(SelectCommand.java:100)
>         at org.apache.hadoop.hbase.hql.HQLClient.executeQuery(HQLClient.java:50)
>         at org.apache.hadoop.hbase.Shell.main(Shell.java:114)
> {code}
> When I look in the .META., I see that the above region range has multiple mentions...
: one offlined, two that have startcodes and servers associated and about 5 others that are
just HRIs.  Table is broke.  At least need the merge of overlapping regions tool to fix. 
Digging more....

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message