You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2008/06/03 20:26:45 UTC

[jira] Created: (HBASE-662) UI in table.jsp gives META locations, not the table's regions location

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


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.


[jira] Commented: (HBASE-662) UI in table.jsp gives META locations, not the table's regions location

Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603642#action_12603642 ] 

Jean-Daniel Cryans commented on HBASE-662:
------------------------------------------

It works for me. On a simple setup, META was on node10, the only user region was on node11 and table.jsp showed that it was on node11.

> 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
>         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.


[jira] Resolved: (HBASE-662) UI in table.jsp gives META locations, not the table's regions location

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Commented: (HBASE-662) UI in table.jsp gives META locations, not the table's regions location

Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603307#action_12603307 ] 

Jean-Daniel Cryans commented on HBASE-662:
------------------------------------------

Will look at it Monday morning. Sorry for all the historian-related problems.

> 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
>         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.


[jira] Updated: (HBASE-662) UI in table.jsp gives META locations, not the table's regions location

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-662:
------------------------

    Attachment: 662-v2.patch

I updated the patch so it applies to trunk.  I tested it but it doesn't seem to fix issue of the tables page showing all regions hosted on the server carrying .META.  Have I broken something?  Does it work for you 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
>         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.


[jira] Updated: (HBASE-662) UI in table.jsp gives META locations, not the table's regions location

Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans updated HBASE-662:
-------------------------------------

    Attachment: hbase-662-v1.patch

Please review.

I changed metaLocation to regionLocation. Returns what you expect.

> 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
>         Attachments: 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.