[
https://issues.apache.org/jira/browse/YARN-11787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan resolved YARN-11787.
-------------------------------
Fix Version/s: 3.5.0
Hadoop Flags: Reviewed
Resolution: Fixed
> [Federation] Enhance Exception Handling in
> FederationClientInterceptor#forceKillApplication
> -------------------------------------------------------------------------------------------
>
> Key: YARN-11787
> URL: https://issues.apache.org/jira/browse/YARN-11787
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: federation
> Affects Versions: 3.5.0, 3.4.2
> Reporter: Shilun Fan
> Assignee: Shilun Fan
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.5.0
>
>
> Currently, when handling {{{}forceKillApplication{}}}, we follow this logic:
> first, we kill the Application in the {{{}HomeSubCluster{}}}, and then kill
> the Applications in the other subclusters. This approach can lead to an issue
> where, if a subcluster does not have the Application, the subcluster's RM
> throws an "application not exists in RM" exception. In this case, we can
> safely ignore the exception as it does not impact our normal processing flow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
