[
https://issues.apache.org/jira/browse/YARN-4606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16423059#comment-16423059
]
Eric Payne commented on YARN-4606:
----------------------------------
{code:title=AppSchedulingInfo#updatePendingResources}
if(! this.schedulerApplicationAttempt.isWaitingForAMContainer()) {
abstractUsersManager.activateApplication(user, applicationId);
}
{code}
Sorry for backtracking, but after thinking about this some more, I think the
question that needs to be asked by {{AppSchedulingInfo#updatePendingResources}}
is not "Is this application attempt asking for an AM?", but rather I think the
question is "Does this user have schedulable apps (including this attempt)?"
I'd like [~sunilg]'s and [~leftnoteasy]'s input on this design suggestion.
> 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, YARN-4606.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: [email protected]
For additional commands, e-mail: [email protected]
