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-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
