[YARN-10219] YARN service placement constraints is broken

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 3.1.0, 3.2.0, 3.1.1, 3.1.2, 3.3.0, 3.2.1, 3.1.3
• Fix Version/s: 3.3.0, 3.4.0
• Component/s: yarn
• Target Version/s: 3.3.0, 3.4.0
• Assignee: Eric Yang Assign to me
• Reporter: Eric Yang
• Created: 01/Apr/20 18:58
• Updated: 26/Jan/24 05:55
• Resolved: 14/Apr/20 07:30

Description

YARN service placement constraint does not work with node label nor node attributes. Example of placement constraints:

 
      "placement_policy": {
        "constraints": [
          {
            "type": "AFFINITY",
            "scope": "NODE",
            "node_attributes": {
              "label":["genfile"]
            },
            "target_tags": [
              "ping"
            ] 
          }
        ]
      },

Node attribute added:

 ./bin/yarn nodeattributes -add "host-3.example.com:label=genfile" 

Scheduling activities shows:

 <diagnostic> Node does not match partition or placement constraints, unsatisfied PC expression="in,node,ping", target-type=ALLOCATION_TAG </diagnostic>
 <count>1</count>
 <nodeIds>host-3.example.com:45454</nodeIds>