You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Eric Payne (JIRA)" <ji...@apache.org> on 2017/12/06 16:51:00 UTC

[jira] [Created] (YARN-7619) Max AM Resource value in CS UI is different for every user

Eric Payne created YARN-7619:
--------------------------------

             Summary: 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: 3.0.0-beta1, 2.9.0, 2.8.2, 3.1.0
            Reporter: Eric Payne
            Assignee: Eric Payne


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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org