hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-662) UI in table.jsp gives META locations, not the table's regions location
Date Tue, 10 Jun 2008 07:55:45 GMT

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

stack resolved HBASE-662.

       Resolution: Fixed
    Fix Version/s: 0.2.0

I committed a version of your patch J-D.  I added a little parser for the meta region rows
to extract table name and the row.  I was finding that your version of the patch worked if
only one region in a table (all regions beyond the first were reported as being hosted on
the same server as was hosting the first region in the table).

Its still not 'perfect' in that the client that is hosted inside the infoserver can have a
stale cache of regions so will report wrong addresses for regions; we can later add a 'force
scan' or some such button so the client's cache gets fixed.

Thanks for the patch J-D.

> UI in table.jsp gives META locations, not the table's regions location
> ----------------------------------------------------------------------
>                 Key: HBASE-662
>                 URL: https://issues.apache.org/jira/browse/HBASE-662
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: client
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>            Priority: Minor
>             Fix For: 0.2.0
>         Attachments: 662-v2.patch, hbase-662-v1.patch
> In HTable.getRegionsInfo()
> {quote}
> regionMap.put(info, metaLocation.getServerAddress());
> {quote}
> That returns the meta region location, not the location of the region of the table.

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

View raw message