[
https://issues.apache.org/jira/browse/YARN-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346808#comment-16346808
]
Sunil G commented on YARN-4606:
-------------------------------
[~maniraj...@gmail.com]
You can look into {{SchedulerApplicationAttempt.isWaitingForAMContainer()}} to
know an app is pending for its AM container. Hence new method
{{activeApplication()}} in {{AppSchedulingInfo is not needed.}}
Ideally we have {{ActiveUsersManager}} which has all the active users in that
cluster (including apps which are pending). I thin we can have
{{activeUsersOfPendingApps along with}} {{activeUsers}} . Hence in case of
scheduling we can depend only on activeUsers. And when we need to know all
active users in cluster (for user-limit computation etc) we might need to use
activeUsers+activeUsersOfPendingApps.
cc/ [~leftnoteasy] [~jlowe] [~eepayne] Could you please help to check this and
share your thoughts.
> CapacityScheduler: applications could get starved because computation of
> #activeUsers considers pending apps
> -------------------------------------------------------------------------------------------------------------
>
> Key: YARN-4606
> URL: https://issues.apache.org/jira/browse/YARN-4606
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler, capacityscheduler
> Affects Versions: 2.8.0, 2.7.1
> Reporter: Karam Singh
> Assignee: Wangda Tan
> Priority: Critical
> Attachments: YARN-4606.1.poc.patch
>
>
> Currently, if all applications belong to same user in LeafQueue are pending
> (caused by max-am-percent, etc.), ActiveUsersManager still considers the user
> is an active user. This could lead to starvation of active applications, for
> example:
> - App1(belongs to user1)/app2(belongs to user2) are active, app3(belongs to
> user3)/app4(belongs to user4) are pending
> - ActiveUsersManager returns #active-users=4
> - However, there're only two users (user1/user2) are able to allocate new
> resources. So computed user-limit-resource could be lower than expected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
