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

Wangda Tan commented on YARN-5889:
----------------------------------

bq. Let's please do these as separate JIRAs. We are extremely anxious to move 
this JIRA forward since it is blocking YARN-2113 (user limit-based intra-queue 
preemption).
I understand, however I prefer to do the refactoring together with the patch, 
If we don't actively do refactoring to make a clean code structure with major 
behavior changes, it will cause a lot of trouble to maintain the code and add 
new functionalities. I'm OK with moving other changes like partition-related 
changes to a separate JIRA if it needs considerable effort. 

> Improve user-limit calculation in capacity scheduler
> ----------------------------------------------------
>
>                 Key: YARN-5889
>                 URL: https://issues.apache.org/jira/browse/YARN-5889
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacity scheduler
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: YARN-5889.0001.patch, 
> YARN-5889.0001.suggested.patchnotes, YARN-5889.v0.patch, YARN-5889.v1.patch, 
> YARN-5889.v2.patch
>
>
> Currently user-limit is computed during every heartbeat allocation cycle with 
> a write lock. To improve performance, this tickets is focussing on moving 
> user-limit calculation out of heartbeat allocation flow.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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