[
https://issues.apache.org/jira/browse/YARN-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970909#comment-14970909
]
Junping Du commented on YARN-4132:
----------------------------------
Thanks for bring out the problem, [~lichangleo]!
I agree that we may want different retry times, intervals (or even retry
policy) for different consumer of RMProxy. However, the current patch way -
have a separated property which override a general property in config at
runtime sounds a little tricky here. We should think if there are some better
way, e.g. passing the parameters in creating RMProxy which will take these
parameters as priority in creating retry policies before taking property in
config as default values. Thoughts?
> Nodemanagers should try harder to connect to the RM
> ---------------------------------------------------
>
> Key: YARN-4132
> URL: https://issues.apache.org/jira/browse/YARN-4132
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Chang Li
> Assignee: Chang Li
> Attachments: YARN-4132.2.patch, YARN-4132.patch
>
>
> Being part of the cluster, nodemanagers should try very hard (and possibly
> never give up) to connect to a resourcemanager. Minimally we should have a
> separate config to set how aggressively a nodemanager will connect to the RM
> separate from what clients will do.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
