[
https://issues.apache.org/jira/browse/HBASE-13479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497098#comment-14497098
]
Esteban Gutierrez commented on HBASE-13479:
-------------------------------------------
lgtm
> [branch-1.0] Master should not bind to region server ports
> ----------------------------------------------------------
>
> Key: HBASE-13479
> URL: https://issues.apache.org/jira/browse/HBASE-13479
> Project: HBase
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Priority: Blocker
> Fix For: 1.0.1
>
> Attachments: hbase-13479_v1.patch
>
>
> In parent jira, we have brought back old config value {{hbase.master.port}}
> and made it so that if it is configured (which is by default), master does
> not bind to the region servers's RPC and info ports now. We have realized
> that master binding to RS ports turns out to be a pain point and unnecessary
> frustration for users (although we were expecting the opposite).
> Let's use this jira to see what we can do in 1.0.x series. In 1.0.0, master
> binds to ports
> {{hbase.regionserver.port}}
> {{hbase.master.info.port}}
> {{hbase.regionserver.info.port}}
> In 1.0.x, we have a couple of options I think:
> (a) don't do anything.
> (b) Commit patch from master as it is. All upgrades from 1.0.0 will observe
> changed ports.
> (c) Commit the patch, disabled by default. If user has {{hbase.master.port}}
> set, bind to the port. Only users who set the conf value will observe changed
> ports.
> (d) Commit the patch with an extra config option
> {{hbase.master.compat.mode}}. The users have to explicitly enable this in
> 1.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
