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

Naganarasimha G R commented on YARN-8102:
-----------------------------------------

[~bibinchundatt],

_There could be deployments with folder level permissions are not given for 
/tmp folder too and user doesn't need the attributes feature ._

Are you referring to the HDFS folder? Which is also very rare to have /tmp to 
be restricted further why not use default dir to be some sub path of  
"${hadoop.tmp.dir}" i.e. local dir ?

 

_Additional advantage is if the deployment is only distributed type then we 
dont require store is implicitly supported. Attribute manager will be alive 
always._

As discussed earlier there is no concept of Distributed or Centralized 
Attributes, both modes can  co exist.

 _profiles are considered based on {{resource-profiles.enabled}} configuration_

May be i am wrong with the exact example quoted by [[email protected]] (i 
just remember something related to resource, and assumed to be resource 
profile).  Nevertheless point here is as far as possible avoid additional 
config and have some defaults if required without affecting the performance. 

> Retrospect on having enable and disable flag for Node Attribute
> ---------------------------------------------------------------
>
>                 Key: YARN-8102
>                 URL: https://issues.apache.org/jira/browse/YARN-8102
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Bibin A Chundatt
>            Assignee: Bibin A Chundatt
>            Priority: Major
>
> Currently node attribute feature is by default enabled. We have to revisit on 
> the same.
> Enabling by default means will try to create store for all cluster 
> installation.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to