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

Weiwei Yang commented on YARN-8925:
-----------------------------------

Hi [~Tao Yang]

Today I applied the patch to a v3.2 cluster. I use configurable based node 
attributes provider.

{code}

<property>
 <name>yarn.node-attribute.fs-store.root-dir</name>
 <value>/home/wwei/hadoop-3.2.0/hadoop-data/yarn/nodeattributes</value>
 </property>

<property>
 <name>yarn.nodemanager.node-attributes.provider</name>
 <value>config</value>
 </property>

<property>
 
<name>yarn.nodemanager.node-attributes.provider.configured-node-attributes</name>
 <value>osType,STRING,redhat:osVersion,STRING,2.8</value>
 </property>

<property>
 <name>yarn.nodemanager.node-attributes.resync-interval-ms</name>
 <value>1000</value>
 </property>

{code}

when I update the node attribute value of \{{osVersion}} from 2.8 to 2.9. It 
was not updated to RM. I checked via 
[http://RM:8088/ws/v1/cluster/nodes.|http://rm:8088/ws/v1/cluster/nodes.] Could 
u pls take a look?

Thanks

> Updating distributed node attributes only when necessary
> --------------------------------------------------------
>
>                 Key: YARN-8925
>                 URL: https://issues.apache.org/jira/browse/YARN-8925
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: 3.2.1
>            Reporter: Tao Yang
>            Assignee: Tao Yang
>            Priority: Major
>              Labels: performance
>         Attachments: YARN-8925.001.patch, YARN-8925.002.patch, 
> YARN-8925.003.patch, YARN-8925.004.patch, YARN-8925.005.patch, 
> YARN-8925.006.patch, YARN-8925.007.patch, YARN-8925.008.patch, 
> YARN-8925.009.patch, YARN-8925.010.patch
>
>
> Currently if distributed node attributes exist, even though there is no 
> change, updating for distributed node attributes will happen in every 
> heartbeat between NM and RM. Updating process will hold 
> NodeAttributesManagerImpl#writeLock and may have some influence in a large 
> cluster. We have found nodes UI of a large cluster is opened slowly and most 
> time it's waiting for the lock in NodeAttributesManagerImpl. I think this 
> updating should be called only when necessary to enhance the performance of 
> related process.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to