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 "Junfan Zhang (Jira)" <ji...@apache.org> on 2022/03/21 14:00:00 UTC

[jira] [Comment Edited] (YARN-11087) Introduce the config to control the refresh interval in RMDelegatedNodeLabelsUpdater

    [ https://issues.apache.org/jira/browse/YARN-11087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509903#comment-17509903 ] 

Junfan Zhang edited comment on YARN-11087 at 3/21/22, 1:59 PM:
---------------------------------------------------------------

What do u think of the second option? [~quapaw] 


was (Author: zuston):
What do u think of the second option? [~snemeth]

> Introduce the config to control the refresh interval in RMDelegatedNodeLabelsUpdater
> ------------------------------------------------------------------------------------
>
>                 Key: YARN-11087
>                 URL: https://issues.apache.org/jira/browse/YARN-11087
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Junfan Zhang
>            Assignee: Junfan Zhang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> h3. Why 
> When configuring nodes to labels mapping by Delegated-Centralized mode, once the newly registered nodes comes, the node-label of this node wont be attached until triggering the nodelabel mapping provider, which the delayed time depends on the scheduler interval.
> h3. How to solve this bug
> I think there are two options
> # Introduce the new config to specify the update-node-label schedule interval. If u want to quickly refresh the newly registered nodes, user should decrease the interval.
> # Once the newly registered node come, directly trigger the execution of nodelabel mapping provider. But if the provider is the time-consuming operation and lots of nodes register to RM  at the same time, this will also make some nodes with node-label delay.
> I prefer the first option and submit the PR to solve this. 
> Feel free to discuss if having any ideas.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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