[
https://issues.apache.org/jira/browse/HBASE-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112754#comment-13112754
]
stack commented on HBASE-4457:
------------------------------
@Praveen I thought about going this route. I couldn't convince myself that
webport was important enough info to make it into the ServerName fundamental
type (its used everywhere, in fs and persisted to zk, serialized over rpc) and
truth be told, I punted on what to do about it; thanks for raising it again.
So I still think having webui port in the servername is not the right place for
it.
What about adding webui param to HMasterRegionInterface#regionServerStartup?
Pass it through to ServerManager.
OnlineServers is ServerName->HServerLoad Map. Maybe the value needs to change
to be a datastructure that has HSL and webui? That would be pretty disruptive?
Perhaps a new ServerInfo or ServerVitals that has HSL and webui? Maybe later
we'll add more 'server info' to this data structure?
I'd almost be ok with a new map of SN->webui that sat beside the onlineServers
and was expired when onlineServer expired........
Sorry if this is more than you bargained for.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
