Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 46E1E18371 for ; Tue, 15 Dec 2015 16:35:47 +0000 (UTC) Received: (qmail 31062 invoked by uid 500); 15 Dec 2015 16:35:47 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 30986 invoked by uid 500); 15 Dec 2015 16:35:47 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 30468 invoked by uid 99); 15 Dec 2015 16:35:46 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2015 16:35:46 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id A6D432C1F70 for ; Tue, 15 Dec 2015 16:35:46 +0000 (UTC) Date: Tue, 15 Dec 2015 16:35:46 +0000 (UTC) From: =?utf-8?Q?Oliv=C3=A9r_Szab=C3=B3_=28JIRA=29?= To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-13038) Define ephemeral port range for Ambari agents MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-13038?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15= 058287#comment-15058287 ]=20 Oliv=C3=A9r Szab=C3=B3 commented on AMBARI-13038: --------------------------------------- Andrew, Yes, I will fix it. Also the port range property would be in better place i= n cluster-env instead of ambari-agent.ini. (and the ranges should be update= d if a config-property is updated too, like "dfs.datanode.https.address" po= rt 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=C3=A9r Szab=C3=B3 > Assignee: Oliv=C3=A9r Szab=C3=B3 > Fix For: 2.4.0 > > Attachments: AMBARI-13038.patch, EphemeralPortRange.pdf > > > Problem:=20 > When Ambari agent starts,it tries to use an ephemeral port that is alread= y 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 servi= ce > Solution: > Range of ephemeral ports used by Ambari should be narrowed. (configurable= ) -- This message was sent by Atlassian JIRA (v6.3.4#6332)