[
https://issues.apache.org/jira/browse/YARN-7469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253721#comment-16253721
]
Eric Payne commented on YARN-7469:
----------------------------------
bq. now min container is the dead zone here
I filed YARN-7501 to include a "dead zone" around the user limit.
bq. in 2.8, this fix has a problem of oscillation due to the difference in how
user limit is calculated between 2.8 and later releases.
[~sunilg], I think this patch should be used to fix the user starvation problem
and the 2.8-specific oscillation problem can be handled by YARN-7496.
{{YARN-7469.001.patch}} will apply cleanly to all branches back to branch-2.8.
> Capacity Scheduler Intra-queue preemption: User can starve if newest app is
> exactly at user limit
> -------------------------------------------------------------------------------------------------
>
> Key: YARN-7469
> URL: https://issues.apache.org/jira/browse/YARN-7469
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacity scheduler, yarn
> Affects Versions: 2.9.0, 3.0.0-beta1, 2.8.2
> Reporter: Eric Payne
> Assignee: Eric Payne
> Attachments: UnitTestToShowStarvedUser.patch, YARN-7469.001.patch
>
>
> Queue Configuration:
> - Total Memory: 20GB
> - 2 Queues
> -- Queue1
> --- Memory: 10GB
> --- MULP: 10%
> --- ULF: 2.0
> - Minimum Container Size: 0.5GB
> Use Case:
> - User1 submits app1 to Queue1 and consumes 20GB
> - User2 submits app2 to Queue1 and requests 7.5GB
> - Preemption monitor preempts 7.5GB from app1. Capacity Scheduler gives those
> resources to User2
> - User 3 submits app3 to Queue1. To begin with, app3 is requesting 1
> container for the AM.
> - Preemption monitor never preempts a container.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
