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 "Varun Saxena (JIRA)" <ji...@apache.org> on 2015/07/29 19:01:04 UTC

[jira] [Assigned] (YARN-3991) Investigate if we need an atomic way to set both memory and CPU on Resource

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

Varun Saxena reassigned YARN-3991:
----------------------------------

    Assignee: Varun Saxena

> Investigate if we need an atomic way to set both memory and CPU on Resource
> ---------------------------------------------------------------------------
>
>                 Key: YARN-3991
>                 URL: https://issues.apache.org/jira/browse/YARN-3991
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.7.1
>            Reporter: Karthik Kambatla
>            Assignee: Varun Saxena
>              Labels: capacityscheduler, fairscheduler, scheduler
>
> While reviewing another patch, noticed that we have independent methods to set memory and CPU. 
> Do we need another method to set them both atomically? Otherwise, would two threads trying to set both values lose any updates? 



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