You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/10/30 08:31:27 UTC

[jira] [Commented] (AMBARI-13038) Define ephemeral port range for Ambari agents

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

Hadoop QA commented on AMBARI-13038:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12757074/EphemeralPortRange.pdf
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4103//console

This message is automatically generated.

> 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)