[
https://issues.apache.org/jira/browse/HBASE-13453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devaraj Das updated HBASE-13453:
--------------------------------
Attachment: 34111-2.txt
The patch addresses the port issue (and yeah it brings back the master port).
It also adds another configuration called hbase.master.regionserver.info.port
that controls what the master's regionserver UI port should be. If both these
configurations are set, the master would start binding to these ports.
> Master should not bind to region server ports
> ---------------------------------------------
>
> Key: HBASE-13453
> URL: https://issues.apache.org/jira/browse/HBASE-13453
> Project: HBase
> Issue Type: Improvement
> Reporter: Enis Soztutar
> Assignee: Devaraj Das
> Priority: Critical
> Fix For: 2.0.0, 1.1.0
>
> Attachments: 34111-2.txt
>
>
> In 1.0, master by default binds to the region server ports (rpc and info). We
> have done it so thinking that in the long term, master and meta co-location
> will be default, and we can merge the master and region server as a single
> daemon.
> Over at HBASE-11165, if the conclusion end up being that meta will not be
> colocated at all, then master hosting a region server will just become an
> implementation detail. [~saint....@gmail.com] says that we might never allow
> master to host regions.
> Now, we are stuck in a state where we have made master bind to RS ports in
> 1.0, which might create some confusion (and frustration) for small cluster
> users who traditionally used to host a master and a region server on the same
> node.
> I think we should undo this in 1.1 and use the previous master ports (16000)
> and not bind to 16030, so that the user does not need to do anything to bring
> up a RS on the same host. At least users going from 0.98 -> 1.1 will not take
> a hit. Users going from 1.0 -> 1.1 will see changed default ports.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
