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 "yehuanhuan (Jira)" <ji...@apache.org> on 2020/06/24 05:34:00 UTC
[jira] [Comment Edited] (YARN-10315) Avoid sending
RMNodeResoureupdate event if resource is same
[ https://issues.apache.org/jira/browse/YARN-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143537#comment-17143537 ]
yehuanhuan edited comment on YARN-10315 at 6/24/20, 5:33 AM:
-------------------------------------------------------------
hi [~Sushil-K-S], Can it be solved by comparing node resource usage before and after processing the completed container at AbstractYarnScheduler#nodeUpdate?
was (Author: yehuanhuan):
Can it be solved by comparing node resource usage before and after processing the completed container at AbstractYarnScheduler#nodeUpdate?
> Avoid sending RMNodeResoureupdate event if resource is same
> -----------------------------------------------------------
>
> Key: YARN-10315
> URL: https://issues.apache.org/jira/browse/YARN-10315
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Bibin Chundatt
> Assignee: Sushil Ks
> Priority: Major
>
> When the node is in DECOMMISSIONING state the RMNodeResourceUpdateEvent is send for every heartbeat . Which will result in scheduler resource update.
> Avoid sending the same.
> Scheduler node resource update iterates through all the queues for resource update which is costly..
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org