hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haibo Chen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-7373) The atomicity of container update in RM is not clear
Date Fri, 20 Oct 2017 18:35:00 GMT
Haibo Chen created YARN-7373:
--------------------------------

             Summary: The atomicity of container update in RM is not clear
                 Key: YARN-7373
                 URL: https://issues.apache.org/jira/browse/YARN-7373
             Project: Hadoop YARN
          Issue Type: Improvement
          Components: resourcemanager
            Reporter: Haibo Chen
            Assignee: Haibo Chen


While reviewing YARN-4511, Miklos pointed out that  
{code:java}
342	    // notify schedulerNode of the update to correct resource accounting
343	    node.containerUpdated(existingRMContainer, existingContainer);
344	
345	    ((RMContainerImpl)tempRMContainer).setContainer(updatedTempContainer);
346	    // notify SchedulerNode of the update to correct resource accounting
347	    node.containerUpdated(tempRMContainer, tempContainer);
348	
{code}
bq. I think that it would be nicer to lock around these two calls to become atomic.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message