[
https://issues.apache.org/jira/browse/HBASE-15355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174245#comment-15174245
]
stack commented on HBASE-15355:
-------------------------------
Mighty [~ghelmling]
"what's the reason for undoing it? We've been considering it as a solution to
situations where the RS hosting meta has a backed up priority queue and master
cannot complete initialization, or if up and running cannot complete region
reassignments for failed servers."
I'd undo it because as-is it is half-baked so disabling till done and we decide
this is the way we want to indeed go (I'd be against it).
+ Because it puts the master in the write path.
+ Won't work for case where we split meta
More (old) discussion here:
https://docs.google.com/document/d/1xC-bCzAAKO59Xo3XN-Cl6p-5CM_4DMoR-WpnkmYZgpw/edit#heading=h.j5yqy7n04bkn
> 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)
