[
https://issues.apache.org/jira/browse/HBASE-10123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142862#comment-15142862
]
Jonathan Hsieh commented on HBASE-10123:
----------------------------------------
Do you have a suggestion on what to do?
The most obvious would be to have one of the systems change their default
ports. I don't have evidence at the moment, but I'd be surprised if there are
more Hadoop kms users than HBase users.
Timeline wise, the changes were released at roughly same time -- This change
was in a released by hbase in 30/oct/2014 [1] and in hadoop 18/nov/2014 [2].
[1] https://archive.apache.org/dist/hbase/hbase-0.99.0/
[2] http://hadoop.apache.org/releases.html
> 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.99.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.3.4#6332)
