[
https://issues.apache.org/jira/browse/YARN-11787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932454#comment-17932454
]
ASF GitHub Bot commented on YARN-11787:
---------------------------------------
slfan1989 opened a new pull request, #7465:
URL: https://github.com/apache/hadoop/pull/7465
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
JIRA: YARN-11787. [Federation] Enhance Exception Handling in
FederationClientInterceptor#forceKillApplication.
### How was this patch tested?
Junit Test.
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> [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
>
> 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-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
