You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Zhang (JIRA)" <ji...@apache.org> on 2019/08/01 23:06:01 UTC
[jira] [Commented] (YARN-9384) FederationInterceptorREST should
broadcast KillApplication to all sub clusters
[ https://issues.apache.org/jira/browse/YARN-9384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16898426#comment-16898426 ]
Zhang commented on YARN-9384:
-----------------------------
[~qiuliang988], No perfect solution. Now KillApplication can only kill containers in home subcluster immediately. Containers from secondary subclusters can continue running for like 10minutes until application in secondary subclusters become "FAILED".
> FederationInterceptorREST should broadcast KillApplication to all sub clusters
> ------------------------------------------------------------------------------
>
> Key: YARN-9384
> URL: https://issues.apache.org/jira/browse/YARN-9384
> Project: Hadoop YARN
> Issue Type: Bug
> Components: federation
> Reporter: Zhang
> Assignee: Zhang
> Priority: Major
> Labels: federation
> Attachments: YARN-9384.2.patch, YARN-9384.patch
>
>
> Today KillApplication request from user client only goes to home cluster. As a result the containers in secondary clusters continue processing for 10~15 minutes (UAM heartbeat timeout).
> This is not an favorable user experience especially when user has a streaming job and sometime needs to restart it (like updating config or resources). In this case, containers created by new job and old job can run at the same time.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org