hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4113) RM should respect retry-interval when uses RetryPolicies.RETRY_FOREVER
Date Mon, 21 Sep 2015 14:36:04 GMT

    [ https://issues.apache.org/jira/browse/YARN-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900752#comment-14900752
] 

Sunil G commented on YARN-4113:
-------------------------------

 Hi [~leftnoteasy] 
I feel test case is not needed as its already covered in HADOOP-12386.will this be fine?

> RM should respect retry-interval when uses RetryPolicies.RETRY_FOREVER
> ----------------------------------------------------------------------
>
>                 Key: YARN-4113
>                 URL: https://issues.apache.org/jira/browse/YARN-4113
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Wangda Tan
>            Assignee: Sunil G
>            Priority: Critical
>         Attachments: 0001-YARN-4113.patch
>
>
> Found one issue in RMProxy how to initialize RetryPolicy: In RMProxy#createRetryPolicy.
When rmConnectWaitMS is set to -1 (wait forever), it uses RetryPolicies.RETRY_FOREVER which
doesn't respect {{yarn.resourcemanager.connect.retry-interval.ms}} setting.
> RetryPolicies.RETRY_FOREVER uses 0 as the interval, when I run the test without properly
setup localhost name: {{TestYarnClient#testShouldNotRetryForeverForNonNetworkExceptions}},
it wrote 14G DEBUG exception message to system before it dies. This will be very bad if we
do the same thing in a production cluster.
> We should fix two places:
> - Make RETRY_FOREVER can take retry-interval as constructor parameter.
> - Respect retry-interval when we uses RETRY_FOREVER policy.



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

Mime
View raw message