[jira] [Updated] (YARN-11509) The FederationInterceptor#launchUAM Added retry logic.
[ https://issues.apache.org/jira/browse/YARN-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shilun Fan updated YARN-11509: -- Parent: YARN-5597 Issue Type: Sub-task (was: Improvement) > The FederationInterceptor#launchUAM Added retry logic. > -- > > Key: YARN-11509 > URL: https://issues.apache.org/jira/browse/YARN-11509 > Project: Hadoop YARN > Issue Type: Sub-task > Components: amrmproxy >Affects Versions: 3.4.0 >Reporter: Shilun Fan >Assignee: Shilun Fan >Priority: Minor > Labels: pull-request-available > Fix For: 3.4.0 > > > There is a "todo" in the > FederationInterceptor#registerAndAllocateWithNewSubClusters method. According > to the "todo" description, the request needs to be retried to other > subclusters, but changing the parameter requests in > registerAndAllocateWithNewSubClusters is not a good operation. It is better > to add retry logic here. > We don't need to worry about losing requests because when the request cannot > be satisfied, the AM of the task will continue to apply, and these requests > will be properly transferred to other clusters for execution. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-11509) The FederationInterceptor#launchUAM Added retry logic.
[ https://issues.apache.org/jira/browse/YARN-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YARN-11509: -- Labels: pull-request-available (was: ) > The FederationInterceptor#launchUAM Added retry logic. > -- > > Key: YARN-11509 > URL: https://issues.apache.org/jira/browse/YARN-11509 > Project: Hadoop YARN > Issue Type: Improvement > Components: amrmproxy >Affects Versions: 3.4.0 >Reporter: Shilun Fan >Assignee: Shilun Fan >Priority: Minor > Labels: pull-request-available > > There is a "todo" in the > FederationInterceptor#registerAndAllocateWithNewSubClusters method. According > to the "todo" description, the request needs to be retried to other > subclusters, but changing the parameter requests in > registerAndAllocateWithNewSubClusters is not a good operation. It is better > to add retry logic here. > We don't need to worry about losing requests because when the request cannot > be satisfied, the AM of the task will continue to apply, and these requests > will be properly transferred to other clusters for execution. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
