[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680812#comment-14680812 ] Wangda Tan commented on YARN-2918: -- [~dheeren], Sorry for the inconvenience. The label where the node labels persisted is specified at: {code} yarn.node-labels.fs-store.root-dir {code} If you don't specify that, it will be /tmp/node-label by default, so I guess your problem is node label dir is cleaned up by OS. > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith Sharma K S >Assignee: Wangda Tan > Labels: 2.6.1-candidate > Fix For: 2.8.0, 2.7.1 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644869#comment-14644869 ] Dheeren Beborrtha commented on YARN-2918: - Thanks Wangda Tan. The problem is that I had a cluster up and running with HDP 2.2.0. Followed HortonWorks instructions to add the labels and configured the CS queues and that was easy.Few days went by. The cluster went down one day and on restart RM wouldn't come back up. The only way we could bring it back was to use an older version of the CS xml to bring it back to life. Unfortunately this was not documented any where. By the way, where are the node labels persisted? I had to re-add the labels too! > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith Sharma K S >Assignee: Wangda Tan > Labels: 2.6.1-candidate > Fix For: 2.8.0, 2.7.1 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643657#comment-14643657 ] Wangda Tan commented on YARN-2918: -- [~dheeren], I think it will be hard to be backported since it's not a simple bug fix. But I added 2.6.1-candidate label to the JIRA to be reviewed. > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith Sharma K S >Assignee: Wangda Tan > Labels: 2.6.1-candidate > Fix For: 2.8.0, 2.7.1 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643650#comment-14643650 ] Dheeren Beborrtha commented on YARN-2918: - This is a major issue and a big inconvenience. Can this be backported to Hadoop 2.6.0? > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith Sharma K S >Assignee: Wangda Tan > Fix For: 2.8.0, 2.7.1 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554556#comment-14554556 ] Hudson commented on YARN-2918: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2150 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2150/]) Move YARN-2918 from 2.8.0 to 2.7.1 (wangda: rev 03f897fd1a3779251023bae358207069b89addbf) * hadoop-yarn-project/CHANGES.txt > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Fix For: 2.8.0, 2.7.1 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554354#comment-14554354 ] Hudson commented on YARN-2918: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #192 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/192/]) Move YARN-2918 from 2.8.0 to 2.7.1 (wangda: rev 03f897fd1a3779251023bae358207069b89addbf) * hadoop-yarn-project/CHANGES.txt > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Fix For: 2.8.0, 2.7.1 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554302#comment-14554302 ] Hudson commented on YARN-2918: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #202 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/202/]) Move YARN-2918 from 2.8.0 to 2.7.1 (wangda: rev 03f897fd1a3779251023bae358207069b89addbf) * hadoop-yarn-project/CHANGES.txt > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Fix For: 2.8.0, 2.7.1 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554235#comment-14554235 ] Hudson commented on YARN-2918: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2132 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2132/]) Move YARN-2918 from 2.8.0 to 2.7.1 (wangda: rev 03f897fd1a3779251023bae358207069b89addbf) * hadoop-yarn-project/CHANGES.txt > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Fix For: 2.8.0, 2.7.1 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554152#comment-14554152 ] Hudson commented on YARN-2918: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #203 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/203/]) Move YARN-2918 from 2.8.0 to 2.7.1 (wangda: rev 03f897fd1a3779251023bae358207069b89addbf) * hadoop-yarn-project/CHANGES.txt > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Fix For: 2.8.0, 2.7.1 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554093#comment-14554093 ] Hudson commented on YARN-2918: -- FAILURE: Integrated in Hadoop-Yarn-trunk #934 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/934/]) Move YARN-2918 from 2.8.0 to 2.7.1 (wangda: rev 03f897fd1a3779251023bae358207069b89addbf) * hadoop-yarn-project/CHANGES.txt > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Fix For: 2.8.0, 2.7.1 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14553158#comment-14553158 ] Hudson commented on YARN-2918: -- FAILURE: Integrated in Hadoop-trunk-Commit #7875 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/7875/]) Move YARN-2918 from 2.8.0 to 2.7.1 (wangda: rev 03f897fd1a3779251023bae358207069b89addbf) * hadoop-yarn-project/CHANGES.txt > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Fix For: 2.8.0, 2.7.1 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14553086#comment-14553086 ] Wangda Tan commented on YARN-2918: -- Back-ported this patch to 2.7.1, updating fix version. > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Fix For: 2.8.0, 2.7.1 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534981#comment-14534981 ] Hudson commented on YARN-2918: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #189 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/189/]) YARN-2918. RM should not fail on startup if queue's configured labels do not exist in cluster-node-labels. Contributed by Wangda Tan (jianhe: rev f489a4ec969f3727d03c8e85d51af1018fc0b2a1) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ApplicationMasterService.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacitySchedulerConfiguration.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMServerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/TestSchedulerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CSQueueUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/AbstractCSQueue.java * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestQueueParsing.java > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Fix For: 2.8.0 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534910#comment-14534910 ] Hudson commented on YARN-2918: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2137 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2137/]) YARN-2918. RM should not fail on startup if queue's configured labels do not exist in cluster-node-labels. Contributed by Wangda Tan (jianhe: rev f489a4ec969f3727d03c8e85d51af1018fc0b2a1) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerUtils.java * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/TestSchedulerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacitySchedulerConfiguration.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CSQueueUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/AbstractCSQueue.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ApplicationMasterService.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestQueueParsing.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMServerUtils.java > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Fix For: 2.8.0 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534782#comment-14534782 ] Hudson commented on YARN-2918: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #179 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/179/]) YARN-2918. RM should not fail on startup if queue's configured labels do not exist in cluster-node-labels. Contributed by Wangda Tan (jianhe: rev f489a4ec969f3727d03c8e85d51af1018fc0b2a1) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMServerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacitySchedulerConfiguration.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/AbstractCSQueue.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CSQueueUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ApplicationMasterService.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/TestSchedulerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestQueueParsing.java > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Fix For: 2.8.0 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534678#comment-14534678 ] Hudson commented on YARN-2918: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2119 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2119/]) YARN-2918. RM should not fail on startup if queue's configured labels do not exist in cluster-node-labels. Contributed by Wangda Tan (jianhe: rev f489a4ec969f3727d03c8e85d51af1018fc0b2a1) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/TestSchedulerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ApplicationMasterService.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestQueueParsing.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMServerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacitySchedulerConfiguration.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/AbstractCSQueue.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CSQueueUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerUtils.java * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Fix For: 2.8.0 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534523#comment-14534523 ] Hudson commented on YARN-2918: -- SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #190 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/190/]) YARN-2918. RM should not fail on startup if queue's configured labels do not exist in cluster-node-labels. Contributed by Wangda Tan (jianhe: rev f489a4ec969f3727d03c8e85d51af1018fc0b2a1) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/TestSchedulerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestQueueParsing.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacitySchedulerConfiguration.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/AbstractCSQueue.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMServerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CSQueueUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ApplicationMasterService.java > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Fix For: 2.8.0 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534484#comment-14534484 ] Hudson commented on YARN-2918: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #921 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/921/]) YARN-2918. RM should not fail on startup if queue's configured labels do not exist in cluster-node-labels. Contributed by Wangda Tan (jianhe: rev f489a4ec969f3727d03c8e85d51af1018fc0b2a1) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/AbstractCSQueue.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMServerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ApplicationMasterService.java * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacitySchedulerConfiguration.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CSQueueUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestQueueParsing.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/TestSchedulerUtils.java > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Fix For: 2.8.0 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533716#comment-14533716 ] Hudson commented on YARN-2918: -- SUCCESS: Integrated in Hadoop-trunk-Commit #7764 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/7764/]) YARN-2918. RM should not fail on startup if queue's configured labels do not exist in cluster-node-labels. Contributed by Wangda Tan (jianhe: rev f489a4ec969f3727d03c8e85d51af1018fc0b2a1) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/AbstractCSQueue.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestQueueParsing.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ApplicationMasterService.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMServerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacitySchedulerConfiguration.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java * hadoop-yarn-project/CHANGES.txt * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/TestSchedulerUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CSQueueUtils.java * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerUtils.java > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Fix For: 2.8.0 > > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533329#comment-14533329 ] Hadoop QA commented on YARN-2918: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | pre-patch | 14m 35s | Pre-patch trunk compilation is healthy. | | {color:green}+1{color} | @author | 0m 0s | The patch does not contain any @author tags. | | {color:green}+1{color} | tests included | 0m 0s | The patch appears to include 2 new or modified test files. | | {color:green}+1{color} | javac | 7m 29s | There were no new javac warning messages. | | {color:green}+1{color} | javadoc | 9m 32s | There were no new javadoc warning messages. | | {color:green}+1{color} | release audit | 0m 22s | The applied patch does not increase the total number of release audit warnings. | | {color:red}-1{color} | checkstyle | 0m 47s | The applied patch generated 5 new checkstyle issues (total was 363, now 367). | | {color:red}-1{color} | whitespace | 0m 12s | The patch has 28 line(s) that end in whitespace. Use git apply --whitespace=fix. | | {color:green}+1{color} | install | 1m 36s | mvn install still works. | | {color:green}+1{color} | eclipse:eclipse | 0m 32s | The patch built with eclipse:eclipse. | | {color:green}+1{color} | findbugs | 1m 15s | The patch does not introduce any new Findbugs (version 2.0.3) warnings. | | {color:green}+1{color} | yarn tests | 52m 56s | Tests passed in hadoop-yarn-server-resourcemanager. | | | | 89m 22s | | \\ \\ || Subsystem || Report/Notes || | Patch URL | http://issues.apache.org/jira/secure/attachment/12731243/YARN-2918.3.patch | | Optional Tests | javadoc javac unit findbugs checkstyle | | git revision | trunk / ab5058d | | checkstyle | https://builds.apache.org/job/PreCommit-YARN-Build/7772/artifact/patchprocess/diffcheckstylehadoop-yarn-server-resourcemanager.txt | | whitespace | https://builds.apache.org/job/PreCommit-YARN-Build/7772/artifact/patchprocess/whitespace.txt | | hadoop-yarn-server-resourcemanager test log | https://builds.apache.org/job/PreCommit-YARN-Build/7772/artifact/patchprocess/testrun_hadoop-yarn-server-resourcemanager.txt | | Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/7772/testReport/ | | Java | 1.7.0_55 | | uname | Linux asf906.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux | | Console output | https://builds.apache.org/job/PreCommit-YARN-Build/7772/console | This message was automatically generated. > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Labels: BB2015-05-TBR > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queu
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533199#comment-14533199 ] Wangda Tan commented on YARN-2918: -- In addition, Test failure of TestFifoScheduler is not related to the patch (ran it locally). > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Labels: BB2015-05-TBR > Attachments: YARN-2918.1.patch, YARN-2918.2.patch, YARN-2918.3.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14533179#comment-14533179 ] Jian He commented on YARN-2918: --- looks good overall, minor comments: - simplify below a bit? {code} boolean queueCheck = true; if (queueLabels == null) { queueCheck = false; } else { if (!queueLabels.contains(str) && !queueLabels.contains(RMNodeLabelsManager.ANY)) { queueCheck = false; } } if (!queueCheck) { return false; } {code} - test newly added test conditions in TestSchedulerUtils seems like some of them are not being tested. > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Labels: BB2015-05-TBR > Attachments: YARN-2918.1.patch, YARN-2918.2.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531878#comment-14531878 ] Hadoop QA commented on YARN-2918: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | pre-patch | 14m 41s | Pre-patch trunk compilation is healthy. | | {color:green}+1{color} | @author | 0m 0s | The patch does not contain any @author tags. | | {color:green}+1{color} | tests included | 0m 0s | The patch appears to include 2 new or modified test files. | | {color:green}+1{color} | javac | 7m 31s | There were no new javac warning messages. | | {color:green}+1{color} | javadoc | 9m 36s | There were no new javadoc warning messages. | | {color:green}+1{color} | release audit | 0m 22s | The applied patch does not increase the total number of release audit warnings. | | {color:red}-1{color} | checkstyle | 0m 52s | The applied patch generated 5 new checkstyle issues (total was 363, now 367). | | {color:red}-1{color} | whitespace | 0m 13s | The patch has 33 line(s) that end in whitespace. Use git apply --whitespace=fix. | | {color:green}+1{color} | install | 1m 35s | mvn install still works. | | {color:green}+1{color} | eclipse:eclipse | 0m 32s | The patch built with eclipse:eclipse. | | {color:green}+1{color} | findbugs | 1m 15s | The patch does not introduce any new Findbugs (version 2.0.3) warnings. | | {color:red}-1{color} | yarn tests | 52m 49s | Tests failed in hadoop-yarn-server-resourcemanager. | | | | 89m 31s | | \\ \\ || Reason || Tests || | Failed unit tests | hadoop.yarn.server.resourcemanager.scheduler.fifo.TestFifoScheduler | \\ \\ || Subsystem || Report/Notes || | Patch URL | http://issues.apache.org/jira/secure/attachment/12731015/YARN-2918.2.patch | | Optional Tests | javadoc javac unit findbugs checkstyle | | git revision | trunk / 31b627b | | checkstyle | https://builds.apache.org/job/PreCommit-YARN-Build/7744/artifact/patchprocess/diffcheckstylehadoop-yarn-server-resourcemanager.txt | | whitespace | https://builds.apache.org/job/PreCommit-YARN-Build/7744/artifact/patchprocess/whitespace.txt | | hadoop-yarn-server-resourcemanager test log | https://builds.apache.org/job/PreCommit-YARN-Build/7744/artifact/patchprocess/testrun_hadoop-yarn-server-resourcemanager.txt | | Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/7744/testReport/ | | Java | 1.7.0_55 | | uname | Linux asf906.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux | | Console output | https://builds.apache.org/job/PreCommit-YARN-Build/7744/console | This message was automatically generated. > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Labels: BB2015-05-TBR > Attachments: YARN-2918.1.patch, YARN-2918.2.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we sh
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14529610#comment-14529610 ] Hadoop QA commented on YARN-2918: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | pre-patch | 14m 38s | Pre-patch trunk compilation is healthy. | | {color:green}+1{color} | @author | 0m 0s | The patch does not contain any @author tags. | | {color:green}+1{color} | tests included | 0m 0s | The patch appears to include 2 new or modified test files. | | {color:green}+1{color} | javac | 7m 33s | There were no new javac warning messages. | | {color:green}+1{color} | javadoc | 9m 35s | There were no new javadoc warning messages. | | {color:green}+1{color} | release audit | 0m 23s | The applied patch does not increase the total number of release audit warnings. | | {color:red}-1{color} | checkstyle | 0m 46s | The applied patch generated 3 new checkstyle issues (total was 363, now 365). | | {color:red}-1{color} | whitespace | 0m 8s | The patch has 38 line(s) that end in whitespace. Use git apply --whitespace=fix. | | {color:green}+1{color} | install | 1m 33s | mvn install still works. | | {color:green}+1{color} | eclipse:eclipse | 0m 34s | The patch built with eclipse:eclipse. | | {color:green}+1{color} | findbugs | 1m 16s | The patch does not introduce any new Findbugs (version 2.0.3) warnings. | | {color:red}-1{color} | yarn tests | 62m 38s | Tests failed in hadoop-yarn-server-resourcemanager. | | | | 99m 9s | | \\ \\ || Reason || Tests || | Timed out tests | org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestNodeLabelContainerAllocation | \\ \\ || Subsystem || Report/Notes || | Patch URL | http://issues.apache.org/jira/secure/attachment/12730632/YARN-2918.1.patch | | Optional Tests | javadoc javac unit findbugs checkstyle | | git revision | trunk / 9809a16 | | checkstyle | https://builds.apache.org/job/PreCommit-YARN-Build/7714/artifact/patchprocess/diffcheckstylehadoop-yarn-server-resourcemanager.txt | | whitespace | https://builds.apache.org/job/PreCommit-YARN-Build/7714/artifact/patchprocess/whitespace.txt | | hadoop-yarn-server-resourcemanager test log | https://builds.apache.org/job/PreCommit-YARN-Build/7714/artifact/patchprocess/testrun_hadoop-yarn-server-resourcemanager.txt | | Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/7714/testReport/ | | Java | 1.7.0_55 | | uname | Linux asf909.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux | | Console output | https://builds.apache.org/job/PreCommit-YARN-Build/7714/console | This message was automatically generated. > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > Attachments: YARN-2918.1.patch > > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that a
[jira] [Commented] (YARN-2918) Don't fail RM if queue's configured labels are not existed in cluster-node-labels
[ https://issues.apache.org/jira/browse/YARN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14528991#comment-14528991 ] Wangda Tan commented on YARN-2918: -- Added more details to description, I plan to do following stuffs in the patch: - Stop checking label's existence while init queue - Continue check label's capacity setting ({{Ī£child-queue.label.capacity = 100}}) - Reject application/resource-request if label is not exist. > Don't fail RM if queue's configured labels are not existed in > cluster-node-labels > - > > Key: YARN-2918 > URL: https://issues.apache.org/jira/browse/YARN-2918 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager >Reporter: Rohith >Assignee: Wangda Tan > > Currently, if admin setup labels on queues > {{.accessible-node-labels = ...}}. And the label is not added to > RM, queue's initialization will fail and RM will fail too: > {noformat} > 2014-12-03 20:11:50,126 FATAL > org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting > ResourceManager > ... > Caused by: java.io.IOException: NodeLabelManager doesn't include label = x, > please check. > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils.checkIfLabelInClusterNodeLabels(SchedulerUtils.java:287) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.AbstractCSQueue.(AbstractCSQueue.java:109) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.(LeafQueue.java:120) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:567) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:587) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initializeQueues(CapacityScheduler.java:462) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:294) > at > org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:324) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > {noformat} > This is not a good user experience, we should stop fail RM so that admin can > configure queue/labels in following steps: > - Configure queue (with label) > - Start RM > - Add labels to RM > - Submit applications > Now admin has to: > - Configure queue (without label) > - Start RM > - Add labels to RM > - Refresh queue's config (with label) > - Submit applications -- This message was sent by Atlassian JIRA (v6.3.4#6332)