[ https://issues.apache.org/jira/browse/YARN-11087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Junfan Zhang updated YARN-11087: -------------------------------- Description: 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. was: 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 > 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 > Priority: Major > Labels: pull-request-available > Time Spent: 10m > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org