[ 
https://issues.apache.org/jira/browse/YARN-8657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625814#comment-16625814
 ] 

Sunil Govindan commented on YARN-8657:
--------------------------------------

{code:java}
}
finally
{
   readLock.unlock();  
}{code}
We use the same now in this new method {{canAssignToUserWithCache}} , correct ?
  

> User limit calculation should be read-lock-protected within LeafQueue
> ---------------------------------------------------------------------
>
>                 Key: YARN-8657
>                 URL: https://issues.apache.org/jira/browse/YARN-8657
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacity scheduler
>            Reporter: Sumana Sathish
>            Assignee: Wangda Tan
>            Priority: Critical
>         Attachments: YARN-8657.001.patch, YARN-8657.002.patch
>
>
> When async scheduling is enabled, user limit calculation could be wrong: 
> It is possible that scheduler calculated a user_limit, but inside 
> {{canAssignToUser}} it becomes staled. 
> We need to protect user limit calculation.



--
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

Reply via email to