[
https://issues.apache.org/jira/browse/YARN-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682595#comment-13682595
]
Alejandro Abdelnur commented on YARN-809:
-----------------------------------------
One thing to keep in mind is that if using Concurrent data strucs, if doing
multiple operations on them you are getting/release locks on them. depending on
the operations those are read/write locks. It may be worth considering to use
non-thread-safe data structures and wrap logical operations in a single
read/write lock block.
> Enable better parallelism in the Fair Scheduler
> -----------------------------------------------
>
> Key: YARN-809
> URL: https://issues.apache.org/jira/browse/YARN-809
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
>
> Currently, the Fair Scheduler is locked on pretty much every operation, node
> updates, application additions and removals, every time the update thread
> runs, and every time the RM queries it for information. Most of this locking
> is unnecessary, especially as only the core scheduling operations like
> application additions, removals, and node updates need a consistent view of
> scheduler state.
> We can probably increase parallelism by using concurrent data structures when
> applicable, as well as keeping a slightly stale view to serve via the RM
> APIs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
