Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 28 Jul 2016 20:04:20 +0000 (UTC)
From: "Chackaravarthy (JIRA)" <jira@apache.org>
To: yarn-dev@hadoop.apache.org
Message-ID: <JIRA.12993350.1469736218000.161413.1469736260585@Atlassian.JIRA>
In-Reply-To: <JIRA.12993350.1469736218000@Atlassian.JIRA>
References: <JIRA.12993350.1469736218000@Atlassian.JIRA> <JIRA.12993350.1469736218789@arcas>
Subject: [jira] [Created] (YARN-5445) Log aggregation configured to
 different namenode can fail fast
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 28 Jul 2016 20:04:25 -0000

Chackaravarthy created YARN-5445:
------------------------------------

             Summary: Log aggregation configured to different namenode can fail fast
                 Key: YARN-5445
                 URL: https://issues.apache.org/jira/browse/YARN-5445
             Project: Hadoop YARN
          Issue Type: Bug
          Components: nodemanager
            Reporter: Chackaravarthy


Log aggregation is enabled and configured to write applogs to different cluster or different namespace (NN federation). In these cases, would like to have some configs on attempts or retries to fail fast in case the other cluster is completely down.

Currently it takes default {{dfs.client.failover.max.attempts}} as 15 and hence adding a latency of 2 to 2.5 mins in each container launch (per node manager).


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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org