[
https://issues.apache.org/jira/browse/HBASE-15355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174303#comment-15174303
]
stack commented on HBASE-15355:
-------------------------------
bq. I disagree. I think the opposite. We didn't go far enough. This master
hosting meta should be default on for 2.0 and I wish it would have been on for
1.0.
You need to make a case. Needs to address the arguments that have come up in
the past: scaling, splitting-meta. See above cited doc and then this one which
you comment on (and in which you seem to have a particular opinion):
https://docs.google.com/document/d/1eCuqf7i2dkWHL0PxcE1HE1nLRQ_tCyXI4JsOB6TAk60/edit#
Looks like we need to revive scaling discussion. It has been underground for a
while now.
> region.jsp can not be found on info server of master
> ----------------------------------------------------
>
> Key: HBASE-15355
> URL: https://issues.apache.org/jira/browse/HBASE-15355
> Project: HBase
> Issue Type: Bug
> Components: UI
> Affects Versions: 2.0.0
> Reporter: Jianwei Cui
> Priority: Minor
>
> After [HBASE-10569|https://issues.apache.org/jira/browse/HBASE-10569], master
> is also a regionserver and it will serve regions of system tables. The meta
> region info could be viewed on master at the address such as :
> http://localhost:16010/region.jsp?name=1588230740. The real path of
> region.jsp for the request will be hbase-webapps/master/region.jsp on master,
> however, the region.jsp is under the directory hbase-webapps/regionserver, so
> that can not be found on master.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
