[
https://issues.apache.org/jira/browse/YARN-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929299#comment-15929299
]
Miklos Szegedi commented on YARN-6244:
--------------------------------------
[~leftnoteasy], I have a question regarding AtomicResource. Is the fact that
{{setMemorySize}} and {{setVirtualCores}} can be called one after another
violating the atomicity? Would it be a good idea to throw an exception, if they
are used within AtomicResource?
> Introduce AtomicResource in ResourceUsage to avoid read-write lock.
> -------------------------------------------------------------------
>
> Key: YARN-6244
> URL: https://issues.apache.org/jira/browse/YARN-6244
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacityscheduler, fairscheduler, resourcemanager,
> scheduler
> Reporter: Wangda Tan
> Attachments: YARN-6244.preliminary.0.patch
>
>
> While doing SLS tests of YARN-5139, I found when multiple threads are doing
> scheduling at the same time, read/write lock of ResourceUsage becomes
> bottleneck. This could be improved.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
