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

ASF GitHub Bot commented on YARN-11412:
---------------------------------------

github-actions[bot] closed pull request #5318: YARN-11412 Concurrent user 
management
URL: https://github.com/apache/hadoop/pull/5318




> Create a Concurrent Users Manager to enable thread safe concurrent resource 
> usage tracking of user
> --------------------------------------------------------------------------------------------------
>
>                 Key: YARN-11412
>                 URL: https://issues.apache.org/jira/browse/YARN-11412
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Krishan Goyal
>            Assignee: Krishan Goyal
>            Priority: Major
>              Labels: pull-request-available
>
> We will build ConcurrentUsersManager whose objective is similar to 
> UsersManager but whose APIs provide better concurrent performance with 
> different class invariants
>  
> Both ConcurrentUsersManager & UsersManager will extend a new class 
> AbstractCSUsersManager which implements AbstractUsersManager
>  
> The primary behavioural change of ConcurrentUsersManager is that it will 
> provide user resource limits which are eventually consistent wrt containers 
> (allocation or release) / users (active or inactive) - These limits affect 
> scheduling and preemption but at massive scale small variances in individual 
> decisions for a container are fine as long as the scheduler progresses in an 
> acceptable way (i.e - users are unconcerned about these variances)
>  
> More details of low level details - 
> [https://docs.google.com/document/d/1czUh2XU3_X_eRIJAsSM40hRuHYSHw4ymyfky39dIj4s/edit]
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to