ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13038) Define ephemeral port range for Ambari agents
Date Fri, 11 Dec 2015 15:21:11 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052893#comment-15052893
] 

Andrew Onischuk commented on AMBARI-13038:
------------------------------------------

The list of most default ephemeral posts :
hdfs-site
"dfs.namenode.http-address": "somehost:50070" -> "somehost:20070"
"dfs.namenode.https-address": "somehost:50470" -> "somehost:20470"
"dfs.namenode.secondary.http-address": "somehost:50090" -> "somehost:20090"
"dfs.datanode.https.address": "0.0.0.0:50475" -> "0.0.0.0:20475"
"dfs.datanode.address": "0.0.0.0:50010" -> "0.0.0.0:20010"
"dfs.datanode.http.address": "0.0.0.0:50075" -> "0.0.0.0:20075"

yarn-site
"yarn.nodemanager.address": "0.0.0.0:45454" -> "0.0.0.0:25454"

hbase-site
"hbase.master.port": "60000" -> "20000"
"hbase.master.info.port": "60010" -> "30010"
"hbase.regionserver.info.port": "60030" -> "20030"

webhcat-site
"templeton.port": "50111" -> "20111"

falcon-startup.properties
"*.broker.url": "tcp://somehost:61616" -> "tcp://somehost:21616"

storm-site (for Ambari 2.0 and lower - in case of upgrade testing)
"supervisor.childopts": "... -Dcom.sun.management.jmxremote.port=56431 ..." -> "... -Dcom.sun.management.jmxremote.port=26431
..."

storm-env (for Ambari 2.1 and higher)
"jmxremote_port": "56431" -> "26431"

ams-site
"timeline.metrics.service.rpc.address": "0.0.0.0:60200" -> "0.0.0.0:20200"

topology (for Knox)
"topology": "... <value>ldap://{{knox_host_name}}:33389</value> ..." -> "...
<value>ldap://{{knox_host_name}}:23389</value> ..."



> Define ephemeral port range for Ambari agents
> ---------------------------------------------
>
>                 Key: AMBARI-13038
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13038
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent
>    Affects Versions: 2.1.0
>         Environment: All
>            Reporter: Olivér Szabó
>            Assignee: Olivér Szabó
>             Fix For: 2.3.0
>
>         Attachments: AMBARI-13038.patch, EphemeralPortRange.pdf
>
>
> Problem: 
> When Ambari agent starts,it tries to use an ephemeral port that is already in use by
another component.
> Steps to Reproduce:
> 1. Install a cluster with Ambari
> 2. Restart the Ambari agent until it takes a port in use by another service
> Solution:
> Range of ephemeral ports used by Ambari should be narrowed. (configurable)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message