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

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

[ 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?

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

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

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