[ https://issues.apache.org/jira/browse/YARN-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434648#comment-16434648 ]
Naganarasimha G R edited comment on YARN-8103 at 4/11/18 10:17 PM: ------------------------------------------------------------------- Thanks [~bibinchundatt], for detailing it out. [~cheersyang], As part of YARN-6856, we decided to have feature specific grouping thats when we introduced *node-attributes* option directly under yarn command instead of placing it as suboption under *rmadmin* option. This was done primarily for two reasons # It would be more ideal to capture all related operations under one heading so that its easier to use. (similar to kubernetes). # Lesser commands to type in the CLI. So what we are planning is which ever sub-option requires admin access will get validated and others will be available for access by all users. so here replace, add and remove will be using *ResourceManagerAdministrationProtocol* and for other options which [~bibinchundatt] was mentioning will be using *ApplicationClientProtocol* And as part of last weeks call we decided to go with first listing which Bibin mentioned. And of the last 3 points mentioned by [~bibinchundatt] 1 & 3 is up for discussion. IMO i thought it better to be grouped together because that was the reason which we introduced a option *node-attributes* . was (Author: naganarasimha): Thanks [~bibinchundatt], for detailing it out. [~cheersyang], As part of YARN-6856, we decided to have feature specific grouping thats when we introduced *node-attributes* option directly under yarn command instead of placing it as suboption under *rmadmin* option. This was done primarily for two reasons # It would be more ideal to capture all related operations under one heading so that its easier to use. (similar to kubernetes). # Lesser commands to type in the CLI. So what we are planning is which ever sub-option requires admin access will get validated and others will be available for access by all users. so here replace, add and remove will be using *ResourceManagerAdministrationProtocol* and for other options which [~bibinchundatt] was mentioning will be using *ApplicationClientProtocol* And as part of last weeks call we decided to go with first 3 list which Bibin mentioned. And of the last 3 points mentioned by [~bibinchundatt] 1 & 3 is up for discussion. IMO i thought it better to be grouped together because that was the reason which we introduced a option *node-attributes* . > Add CLI interface to query node attributes > ------------------------------------------- > > Key: YARN-8103 > URL: https://issues.apache.org/jira/browse/YARN-8103 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Bibin A Chundatt > Assignee: Bibin A Chundatt > Priority: Major > > YARN-8100 will add API interface for querying the attributes. CLI interface > for querying node attributes for each nodes and list all attributes in > cluster. -- 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