Log aggregation configured to different namenode can fail fast

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