You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Li Lu (JIRA)" <ji...@apache.org> on 2015/04/02 21:40:53 UTC

[jira] [Updated] (YARN-3440) ResourceUsage should be copy-on-write

     [ https://issues.apache.org/jira/browse/YARN-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Li Lu updated YARN-3440:
------------------------
    Description: 
In {{org.apache.hadoop.yarn.server.resourcemanager.scheduler.ResourceUsage}}, even if it is thread-safe, but Resource returned by getters could be updated by another thread.

All Resource objects in ResourceUsage should be copy-on-write, reader will always get a non-changed Resource. And changes apply on Resource acquired by caller will not affect original Resource.

  was:
In {{org.apache.hadoop.yarn.server.resourcemanager.scheduler.ResourceUsage
}}, even if it is thread-safe, but Resource returned by getters could be updated by another thread.

All Resource objects in ResourceUsage should be copy-on-write, reader will always get a non-changed Resource. And changes apply on Resource acquired by caller will not affect original Resource.


> ResourceUsage should be copy-on-write
> -------------------------------------
>
>                 Key: YARN-3440
>                 URL: https://issues.apache.org/jira/browse/YARN-3440
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager, scheduler, yarn
>            Reporter: Wangda Tan
>            Assignee: Li Lu
>
> In {{org.apache.hadoop.yarn.server.resourcemanager.scheduler.ResourceUsage}}, even if it is thread-safe, but Resource returned by getters could be updated by another thread.
> All Resource objects in ResourceUsage should be copy-on-write, reader will always get a non-changed Resource. And changes apply on Resource acquired by caller will not affect original Resource.



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