[
https://issues.apache.org/jira/browse/HBASE-15355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174330#comment-15174330
]
Gary Helmling commented on HBASE-15355:
---------------------------------------
In my opinion, consistency and availability of meta for master writes make a
pretty strong case. The argument that master is in the write path only applies
because we haven't rolled this completely forward and made master functions
just a special case of the regionserver hosting meta. That seems like the real
endpoint -- the end of master as it's own additional operational process.
Also if we need to split meta for scaling, do we really think we won't also
need to split/distribute master functions for scaling. When looking at hosting
millions of regions, do we really think a single master in the current
incarnation is going to be able to keep up?
> 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)
