[YARN-3409] Support Node Attribute functionality

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.2.0
• Component/s: api, client, RM
• Release Note: With this feature task, Node Attributes is supported in YARN which will help user's to effectively use resources and assign to applications based on characteristics of each node's in the cluster.
• Assignee: Naganarasimha G R
• Reporter: Wangda Tan
• Created: 27/Mar/15 16:45
• Updated: 05/Nov/18 18:19
• Resolved: 12/Sep/18 11:52

Description

Specify only one label for each node (IAW, partition a cluster) is a way to determinate how resources of a special set of nodes could be shared by a group of entities (like teams, departments, etc.). Partitions of a cluster has following characteristics:

• Cluster divided to several disjoint sub clusters.
• ACL/priority can apply on partition (Only market team / marke team has priority to use the partition).
• Percentage of capacities can apply on partition (Market team has 40% minimum capacity and Dev team has 60% of minimum capacity of the partition).

Attributes are orthogonal to partition, they’re describing features of node’s hardware/software just for affinity. Some example of attributes:

• glibc version
• JDK version
• Type of CPU (x86_64/i686)
• Type of OS (windows, linux, etc.)

With this, application can be able to ask for resource has (glibc.version >= 2.20 && JDK.version >= 8u20 && x86_64).

Issue Links

• Dependency: YARN-8670 Support scheduling request for SLS input and attributes for Node in SLS
• is depended upon by: YARN-6720 Support updating FPGA related constraint node label after FPGA device re-configuration
• is depended upon by: YARN-8766 Support for Node Attribute Functionality, Phase 2
• is related to: YARN-5683 Support specifying storage type for per-application local dirs
• is related to: YARN-2492 (Clone of YARN-796) Allow for (admin) labels on nodes and resource-requests
• relates to: YARN-6346 Expose API in ApplicationSubmissionContext to specify placement constraints

Sub-Tasks

• CLI Proto Modifications to support Node Attributes: Resolved
• Support CLI for Node Attributes Mapping: Resolved
• Attribute Manager to store and provide node attributes in RM: Resolved
• Support distributed node attributes: Resolved
• Refactor NodeLabelsProvider to be more generic and reusable for node attributes providers: Resolved
• Update PB for prefix support of node attributes: Resolved
• PB changes to carry node-attributes in NM heartbeat: Resolved
• Attach prefixes to different type of node attributes: Resolved
• Validate Node Attributes from NM: Resolved
• Modify placement constraints to support node attributes: Resolved
• Node attributes documentation: Resolved
• Node attributes reporting from NM to RM: Resolved
• Node Attribute store for storing and recovering attributes: Resolved
• Revisit NodeAttribute class structure: Resolved
• NodeAttributeManager add/get API is not working properly: Resolved
• Refactor FSNodeLabelStore code for Node Attributes store support: Resolved
• Node attribute prefix definition and validation: Resolved
• Expose Node Attributes info via RM nodes REST API: Resolved
• Support configuration based Node Attribute provider: Resolved
• Support API interface to query cluster attributes and attribute to nodes: Resolved
• Add CLI interface to query node attributes: Resolved
• CLI Integration with NodeAttributesManagerImpl: Resolved
• Add API to fetch node to attribute mapping: Resolved
• Fix TestRMWebServicesNodes test failure: Resolved
• Modify distributedshell to support Node Attributes: Resolved
• Node attribute manager logs are flooding RM logs: Resolved
• Allow dot in attribute values: Resolved
• Merge related work for YARN-3409: Resolved
• Relax NE node-attribute check when attribute doesn't exist on a node: Resolved
• Fix jenkins issues for Node Attributes branch: Resolved
• Clear node attribute path after each test run: Resolved