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

ASF GitHub Bot commented on YARN-11566:
---------------------------------------

slfan1989 commented on code in PR #6068:
URL: https://github.com/apache/hadoop/pull/6068#discussion_r1325818204


##########
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/amrmproxy/FederationInterceptor.java:
##########
@@ -897,9 +897,16 @@ public void setNextInterceptor(RequestInterceptor next) {
    * release all the resources that we are holding in this call.
    */
   @Override
-  public void shutdown() {
+  public void shutdown(boolean stop) {

Review Comment:
   YARN-6848 plans to unify the Interceptor interface. Can we not change the 
shutdown parameters? Are there any other ways we can solve the issue?





> Yarn app kill command can not kill the application in secondary sub cluster.
> ----------------------------------------------------------------------------
>
>                 Key: YARN-11566
>                 URL: https://issues.apache.org/jira/browse/YARN-11566
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: zhengchenyu
>            Assignee: zhengchenyu
>            Priority: Major
>              Labels: pull-request-available
>
> When AMRMProxy is enable, the application may allocate container among multi 
> sub cluster. The application in secondary sub cluster will be labeled as 
> unmananged application. When we run 'yarn app -kill \{appid}', the unmananged 
> application will not be killed in secondary sub cluster.
> The unmanaged application will be removed util app attempt is expired after 
> 15 minute.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to