[ https://issues.apache.org/jira/browse/AMBARI-13038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14803203#comment-14803203
]
Olivér Szabó commented on AMBARI-13038:
---------------------------------------
Default range provided by the OS. If you redefine this, that is not take effect on the running
services so it should work with upgrades too. It could be a problem only if someone use specific
ranges on the agent machines, and then this settings is rewrite them. In that case this property
(ephemeral_port_range) should not be there by default or customer has to know to use their
own setting.
> 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.2.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)
|