hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chackaravarthy (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-5445) Log aggregation configured to different namenode can fail fast
Date Thu, 28 Jul 2016 20:04:20 GMT
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-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message