[ https://issues.apache.org/jira/browse/YARN-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533705#comment-14533705 ]
Jun Gong commented on YARN-3480: -------------------------------- [~jianhe], thanks for your comments and suggestion. The latest patch(YARN-3480.03.patch) have been working as expected: just remove the attempt records that's beyond the validity window. For the special case that the validity window is -1, it might be better to remove attempts until the number of attempts is less than hard limit, because yarn.resourcemanager.am.max-attempts might be very large(like our scenario) . What's you option? > Make AM max attempts stored in RMAppImpl and RMStateStore to be configurable > ---------------------------------------------------------------------------- > > Key: YARN-3480 > URL: https://issues.apache.org/jira/browse/YARN-3480 > Project: Hadoop YARN > Issue Type: Improvement > Components: resourcemanager > Affects Versions: 2.6.0 > Reporter: Jun Gong > Assignee: Jun Gong > Attachments: YARN-3480.01.patch, YARN-3480.02.patch, > YARN-3480.03.patch > > > When RM HA is enabled and running containers are kept across attempts, apps > are more likely to finish successfully with more retries(attempts), so it > will be better to set 'yarn.resourcemanager.am.max-attempts' larger. However > it will make RMStateStore(FileSystem/HDFS/ZK) store more attempts, and make > RM recover process much slower. It might be better to set max attempts to be > stored in RMStateStore. > BTW: When 'attemptFailuresValidityInterval'(introduced in YARN-611) is set to > a small value, retried attempts might be very large. So we need to delete > some attempts stored in RMStateStore and RMStateStore. -- This message was sent by Atlassian JIRA (v6.3.4#6332)