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 "Xianghao Lu (Jira)" <ji...@apache.org> on 2019/11/07 07:48:00 UTC
[jira] [Comment Edited] (YARN-9957) The first container we recover
may not be the AM
[ https://issues.apache.org/jira/browse/YARN-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969006#comment-16969006 ]
Xianghao Lu edited comment on YARN-9957 at 11/7/19 7:47 AM:
------------------------------------------------------------
The failure above has nothing to do with the patch, [~asuresh] [~rkanter], Can you please review the patch?
was (Author: luxianghao):
The failure above has nothing to do with the patch, [~arun.suresh@gmail.com] [~rkanter], Can you please review the patch?
> The first container we recover may not be the AM
> ------------------------------------------------
>
> Key: YARN-9957
> URL: https://issues.apache.org/jira/browse/YARN-9957
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
> Affects Versions: 2.9.1
> Reporter: Xianghao Lu
> Assignee: Xianghao Lu
> Priority: Major
> Fix For: 2.9.1
>
> Attachments: 1.jpg, 2.jpg, YARN-9957-branch-2.9.1.001.patch
>
>
> YARN-7382 says that if not running unmanaged, the first container we recover is always the AM, however, the actual situation is not like this, this can lead to a wrong am resource usage after rm recover.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org