[YARN-4454] NM to nodelabel mapping going wrong after RM restart - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Critical
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 2.8.0, 3.0.0-alpha1
Component/s: None
Labels:
None

Description

Nodelabel mapping with NodeManager is going wrong if combination of hostname and then NodeId is used to update nodelabel mapping

Steps to reproduce

1.Create cluster with 2 NM
2.Add label X,Y to cluster
3.replace Label of node 1 using <HOSTNAME1:PORT>,x
4.replace label for node 1 by <HOSTNAME1>,y
5.Again replace label of node 1 by <HOSTNAME1:PORT>,x

Check cluster label mapping HOSTNAME1 will be mapped with X

Now restart RM 2 times NODE LABEL mapping of HOSTNAME1:PORT changes to Y

2015-12-14 17:17:54,901 INFO org.apache.hadoop.yarn.nodelabels.CommonNodeLabelsManager: Add labels: [<ResourcePool_1:exclusivity=true>,<ResourcePool_null:exclusivity=true>]
2015-12-14 17:17:54,905 INFO org.apache.hadoop.yarn.nodelabels.CommonNodeLabelsManager: REPLACE labels on nodes:
2015-12-14 17:17:54,906 INFO org.apache.hadoop.yarn.nodelabels.CommonNodeLabelsManager:   NM=host-10-19-92-188:64318, labels=[ResourcePool_1]
2015-12-14 17:17:54,906 INFO org.apache.hadoop.yarn.nodelabels.CommonNodeLabelsManager:   NM=host-10-19-92-188:0, labels=[ResourcePool_null]
2015-12-14 17:17:54,906 INFO org.apache.hadoop.yarn.nodelabels.CommonNodeLabelsManager:   NM=host-10-19-92-187:64318, labels=[ResourcePool_null]

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

test.patch
18/Dec/15 15:01
5 kB
Bibin Chundatt
0001-YARN-4454.patch
20/Dec/15 13:46
7 kB
Bibin Chundatt

Issue Links

is related to

YARN-2492 (Clone of YARN-796) Allow for (admin) labels on nodes and resource-requests

Open

Activity

People

Assignee:: Bibin Chundatt

Reporter:: Bibin Chundatt

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Dates

Created:: 14/Dec/15 15:45

Updated:: 30/Aug/16 01:13

Resolved:: 21/Dec/15 19:32