[jira] [Updated] (YARN-4454) NM to nodelabel mapping going wrong after RM restart
[ https://issues.apache.org/jira/browse/YARN-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4454: --- Attachment: 0001-YARN-4454.patch Hi [~leftnoteasy] Thank you for looking into the issue . i was checking how to keep the order based on insertion order. Thts not required since when *host* is used all other labels we are getting updated in replace. Your solution totally make sense. Currently before internal label update for the normalize have used treeMap to keep sorting based on Node ID is required. Please do review the same. > NM to nodelabel mapping going wrong after RM restart > > > Key: YARN-4454 > URL: https://issues.apache.org/jira/browse/YARN-4454 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bibin A Chundatt >Assignee: Bibin A Chundatt >Priority: Critical > Attachments: 0001-YARN-4454.patch, test.patch > > > *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 ,x > 4.replace label for node 1 by ,y > 5.Again replace label of node 1 by ,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 > {noformat} > 2015-12-14 17:17:54,901 INFO > org.apache.hadoop.yarn.nodelabels.CommonNodeLabelsManager: Add labels: >
[jira] [Updated] (YARN-4454) NM to nodelabel mapping going wrong after RM restart
[ https://issues.apache.org/jira/browse/YARN-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4454: --- Attachment: test.patch Attaching testcode to reproduce the same > NM to nodelabel mapping going wrong after RM restart > > > Key: YARN-4454 > URL: https://issues.apache.org/jira/browse/YARN-4454 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bibin A Chundatt >Assignee: Bibin A Chundatt >Priority: Critical > Attachments: test.patch > > > *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 ,x > 4.replace label for node 1 by ,y > 5.Again replace label of node 1 by ,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 > {noformat} > 2015-12-14 17:17:54,901 INFO > org.apache.hadoop.yarn.nodelabels.CommonNodeLabelsManager: Add labels: >
[jira] [Updated] (YARN-4454) NM to nodelabel mapping going wrong after RM restart
[ https://issues.apache.org/jira/browse/YARN-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4454: --- Description: *Nodelabel mapping with NodeManager is going wrong if combination of hostname and then NodeId is used* *Steps to reproduce* 1.Create cluster with 2 NM 2.Add label X,Y to cluster 3.replace Label of node 1 using ,x 4.replace label for node 1 by ,y 5.Again replace label of node 1 by ,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 {noformat} 2015-12-14 17:17:54,901 INFO org.apache.hadoop.yarn.nodelabels.CommonNodeLabelsManager: Add labels:
[jira] [Updated] (YARN-4454) NM to nodelabel mapping going wrong after RM restart
[ https://issues.apache.org/jira/browse/YARN-4454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4454: --- 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 ,x 4.replace label for node 1 by ,y 5.Again replace label of node 1 by ,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 {noformat} 2015-12-14 17:17:54,901 INFO org.apache.hadoop.yarn.nodelabels.CommonNodeLabelsManager: Add labels: