[
https://issues.apache.org/jira/browse/HBASE-10483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14223849#comment-14223849
]
Enis Soztutar commented on HBASE-10483:
---------------------------------------
Sorry for coming to this later. I was going over the methods in Admin, and
bumped into this. I think we should not have the method
Admin.getMasterInfoPort(). The reasoning is that, that method will only return
the active master's info port, but not any other detail about the active
master. So you have to obtain the hostname of the active master one way, and
obtain the info port some other way. That means when the master is failing over
etc, it can go out of sync.
For region server info ports, we did a hacky-ish way of adding the info port to
the ServerLoad object. Since master and RS are the same daemon now, their info
port is the same? Can we create a follow up jira to either change the method to
return the full information for the active master or remove the method and rely
on ClusterStatus ?
> Provide API for retrieving info port when hbase.master.info.port is set to 0
> ----------------------------------------------------------------------------
>
> Key: HBASE-10483
> URL: https://issues.apache.org/jira/browse/HBASE-10483
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: Liu Shaohui
> Fix For: 2.0.0, 0.99.2
>
> Attachments: HBASE-10483-trunk-v1.diff, HBASE-10483-trunk-v2.diff,
> HBASE-10483-v3.diff, HBASE-10483-v4.diff, HBASE-10483-v5.diff
>
>
> When hbase.master.info.port is set to 0, info port is dynamically determined.
> An API should be provided so that client can retrieve the actual info port.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
