[
https://issues.apache.org/jira/browse/YARN-11566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764465#comment-17764465
]
zhengchenyu edited comment on YARN-11566 at 9/13/23 10:00 AM:
--------------------------------------------------------------
There are three ways to solve this problem:
(1) Call forceKillApplication on all sub cluster.
(2) Store secondary sub cluster when submit unmanaged application, then
forceKillApplication on these secondary sub cluster.
(3) forceKillApplication to secondary sub cluster when application is removed
in nodemanager.
was (Author: zhengchenyu):
There are two ways to solve this problem:
(1) Call forceKillApplication on all sub cluster.
(2) Store secondary sub cluster when submit unmanaged application, then
forceKillApplication on these secondary sub cluster.
> 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
>
> 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.
--
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
