hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (YARN-3440) ResourceUsage should be copy-on-write
Date Thu, 02 Apr 2015 18:42:54 GMT

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

Li Lu reassigned YARN-3440:
---------------------------

    Assignee: Li Lu

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

Mime
View raw message