[
https://issues.apache.org/jira/browse/HBASE-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126063#comment-13126063
]
stack commented on HBASE-4457:
------------------------------
Temporary fix sounds good J-D.
And after talking more w/ J-D, one scenario we don't handle w/ the above
suggested passing of webuiport on regionserver start is case where all
regionservers are already floating when the master comes up. In this
situation, there will be no start message on which the regionserver volunteers
UI port -- regionservers are just heartbeating. Unless we made regionservers
rerun their start message -- which we might want to do someday though, could be
issues if the new master tried passing config that was different from what the
regionserver stared with -- or we have master persist regionserver stats to zk
(or when regionserver registers in zk, in its payload it puts its vitals such
as webuiport... which we might want to do) a new master rising into an
already-running cluster would be a little hosed.
> Starting region server on non-default info port is resulting in broken URL's
> in master UI
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-4457
> URL: https://issues.apache.org/jira/browse/HBASE-4457
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.92.0
> Reporter: Praveen Patibandla
> Priority: Minor
> Labels: newbie
> Fix For: 0.92.0
>
> Attachments: 4457-V1.patch, 4457.patch
>
>
> When "hbase.regionserver.info.port" is set to non-default port, Master UI
> has broken URL's in the region server table because it's hard coded to
> default port.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
