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 "Eric Payne (JIRA)" <ji...@apache.org> on 2018/01/04 21:30:00 UTC
[jira] [Commented] (YARN-7619) Max AM Resource value in CS UI is
different for every user
[ https://issues.apache.org/jira/browse/YARN-7619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312057#comment-16312057 ]
Eric Payne commented on YARN-7619:
----------------------------------
Hi [~sunilg]. Thanks again for the reviews and suggestions. FYI, These patches still apply to their respective branches:
- YARN-7619.005.patch:
-- applies only to 3.1
- YARN-7619.005.branch-3.0.patch:
-- applies to branch-3.0 and cherry-picks cleanly to branch-2 and branch-2.9
- YARN-7619.005.branch-2.8.patch:
-- applies to branch-2.8
{quote}
+1 to latest patch. Thanks Eric Payne
I could commit later tomorrow if no objections.
{quote}
Will you get a chance to commit this? Thanks.
> Max AM Resource value in CS UI is different for every user
> ----------------------------------------------------------
>
> Key: YARN-7619
> URL: https://issues.apache.org/jira/browse/YARN-7619
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler, yarn
> Affects Versions: 2.9.0, 3.0.0-beta1, 2.8.2, 3.1.0
> Reporter: Eric Payne
> Assignee: Eric Payne
> Attachments: Max AM Resources is Different for Each User.png, YARN-7619.001.patch, YARN-7619.002.patch, YARN-7619.003.patch, YARN-7619.004.branch-2.8.patch, YARN-7619.004.branch-3.0.patch, YARN-7619.004.patch, YARN-7619.005.branch-2.8.patch, YARN-7619.005.branch-3.0.patch, YARN-7619.005.patch
>
>
> YARN-7245 addressed the problem that the {{Max AM Resource}} in the capacity scheduler UI used to contain the queue-level AM limit instead of the user-level AM limit. It fixed this by using the user-specific AM limit that is calculated in {{LeafQueue#activateApplications}}, stored in each user's {{LeafQueue#User}} object, and retrieved via {{UserInfo#getResourceUsageInfo}}.
> The problem is that this user-specific AM limit depends on the activity of other users and other applications in a queue, and it is only calculated and updated when a user's application is activated. So, when {{CapacitySchedulerPage}} retrieves the user-specific AM limit, it is a stale value unless an application was recently activated for a particular user.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org