Manikandan R commented on YARN-4606:

{quote}I suspect it may be the first case. Please check to make sure your queue 
configuration is set to allow multiple running users in the queue.
Yes, you are right. I can able to run App2 by User 2 after making the config 
changes. On the other hand, With the patch, container is not getting allocated 
to App2's AM while App1 is running.
{quote}The concern is that even though they may be in both FSQueueMetrics, and 
CSQueueMetrics, they are not accessible at the abstract QueueMetrics layer 
because they have different accessors. It should be possible to add a new, 
abstract accessor in QueueMetrics that is implemented in FS/CS QueueMetrics.
Yes, something similar can be done in Abstract class level to achieve this if 

> 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

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to