ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivér Szabó (JIRA) <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13038) Define ephemeral port range for Ambari agents
Date Tue, 15 Dec 2015 16:35:46 GMT

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

Olivér Szabó commented on AMBARI-13038:
---------------------------------------

Andrew,
Yes, I will fix it. Also the port range property would be in better place in cluster-env instead
of ambari-agent.ini. (and the ranges should be updated if a config-property is updated too,
like "dfs.datanode.https.address" port is changed etc.) In a few days, I will start to work
on that.

> 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.4.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