[
https://issues.apache.org/jira/browse/HBASE-10123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh updated HBASE-10123:
-----------------------------------
Release Note:
After 0.98 hbase's default ports have changed to be outside of the ephemeral
port range:.
hbase.master.port : 60000 -> 16000
hbase.master.info.port (http): 60010 -> 16010
hbase.regionserver.port : 60020 -> 16020
hbase.regionserver.info.port (http): 60030 -> 16030
hbase.status.multicast.port : 60100 -> 16100
HBase up to and including 0.98.x chose default tcp ports in the 600xx port
range which conflicts with the standard unix/linux ephmeral port range of
49152-65535 or 32768-61000. This meant if any other processes chose to bind to
a os specified port it could bind to the ports that hbase had as default. If
hbase processes were restarted some hbase nodes would fail to start. The
probability of this happening increases as the number of nodes in the cluster
increases.
Hadoop Flags: Incompatible change,Reviewed
> Change default ports; move them out of linux ephemeral port range
> -----------------------------------------------------------------
>
> Key: HBASE-10123
> URL: https://issues.apache.org/jira/browse/HBASE-10123
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.1.1
> Reporter: stack
> Assignee: Jonathan Hsieh
> Priority: Critical
> Fix For: 0.98.0
>
> Attachments: hbase-10123.patch, hbase-10123.v2.patch,
> hbase-10123.v3.patch, hbase-10123.v4.patch
>
>
> Our defaults clash w/ the range linux assigns itself for creating come-and-go
> ephemeral ports; likely in our history we've clashed w/ a random, short-lived
> process. While easy to change the defaults, we should just ship w/ defaults
> that make sense. We could host ourselves up into the 7 or 8k range.
> See http://www.ncftp.com/ncftpd/doc/misc/ephemeral_ports.html
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
