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 "Yeliang Cang (JIRA)" <ji...@apache.org> on 2018/07/14 08:24:00 UTC
[jira] [Commented] (YARN-8537) Misleading note in FSAppAttempt
class
[ https://issues.apache.org/jira/browse/YARN-8537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16544113#comment-16544113 ]
Yeliang Cang commented on YARN-8537:
------------------------------------
Sorry, it seems that branch-3.1.0 does not have the problem any more.
I discovered this problem in branch-2.7.3 after apply patch YARN-4090, YARN7382.
Restart ResourceManager when there are jobs still running, and the first container that recovered for each job is not the am. And therefore queue's
AMResourceUsage is not correct.
But I can not find this problem in branch-3.1.0, will close this as invalid. Sorry to disturb...
> Misleading note in FSAppAttempt class
> -------------------------------------
>
> Key: YARN-8537
> URL: https://issues.apache.org/jira/browse/YARN-8537
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 3.1.0
> Reporter: Yeliang Cang
> Assignee: Yeliang Cang
> Priority: Minor
>
> In o.a.h.y.s.r.scheduler.fair.FSAppAttempt class, the note below:
> {code}
> // If not running unmanaged, the first container we recover is always
> // the AM. Set the amResource for this app and update the leaf queue's AM
> // usage
> {code}
> In fact, the first container that recovered on my machine mostly is not the AM!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org