[
https://issues.apache.org/jira/browse/HBASE-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880660#action_12880660
]
Lars George commented on HBASE-1748:
------------------------------------
OK, I finally have one cluster updated to 0.20.5 and backported the patch. But
trying this now reveals a major flaw, the backup master does not run nor start
its UI until it has taken over the ZK node. So in effect the backup master is
sleeping and not being able to redirect anything. And once it wakes up and
takes over, the old is considered gone or will sleep subsequently. All in all
the approach with a redirect on the master is futile.
We could change it so that the region servers redirect to the active master so
as not to have to search for it and avoid confusion upon master switches.
Currently we have a separate port for each UI, we could have the regions server
webapp have a specific JSP that redirects to the active master like so?
http://<regionserver>:60030/master.jsp
Anything else is weird. Imagine you have three standby masters and once they
are being used, how do you know how to contact the current active one? The
address is in ZK but we are talking UI here, and at that time the only UI that
still (may) respond is of a known region server.
Any suggestions?
> ClusterStatus needs to print out who has master role
> ----------------------------------------------------
>
> Key: HBASE-1748
> URL: https://issues.apache.org/jira/browse/HBASE-1748
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Priority: Trivial
> Fix For: 0.21.0
>
> Attachments: HBASE-1748.patch
>
>
> Is in zk_dump but not in clusterstatus.
> You need it when you have 5 masters and you are trying to find the UI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
