[
https://issues.apache.org/jira/browse/YARN-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15684977#comment-15684977
]
Yufei Gu edited comment on YARN-5890 at 11/21/16 10:48 PM:
-----------------------------------------------------------
Thanks [[email protected]] for the review. I've uploaded the new
patch for your comments.
The case that fair share is not 0 but so low that we cannot launch any AM is
kind of out of scope of the JIRA. We can definitely cover it later in other
JIRA.
For the clause {{memCapacity - 1024}}, 1024 refers to the AM resource used in
the queue, so I use {{amResource.getMemorySize()}} to get it.
was (Author: yufeigu):
Thanks [[email protected]] for the review. I've uploaded the new
patch for your comments.
> FairScheduler should log information about AM-resource-usage and max-AM-share
> for queues
> ----------------------------------------------------------------------------------------
>
> Key: YARN-5890
> URL: https://issues.apache.org/jira/browse/YARN-5890
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: fairscheduler
> Reporter: Yufei Gu
> Assignee: Yufei Gu
> Attachments: YARN-5890.001.patch, YARN-5890.002.patch
>
>
> There are several cases where jobs in a queue or stuck likely because of
> maxAMShare. It is hard to debug these issues without any information.
> At the very least, we need to log both AM-resource-usage and max-AM-share for
> queues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
