[jira] [Commented] (YARN-2669) FairScheduler: queueName shouldn't allow periods the allocation.xml

[ https://issues.apache.org/jira/browse/YARN-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168938#comment-14168938 ] Wei Yan commented on YARN-2669: --- The generated release audit is not related to this patch. >

[jira] [Commented] (YARN-2669) FairScheduler: queueName shouldn't allow periods the allocation.xml

[ https://issues.apache.org/jira/browse/YARN-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168935#comment-14168935 ] Hadoop QA commented on YARN-2669: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-2674) Distributed shell AM may re-launch containers if RM work preserving restart happens

[ https://issues.apache.org/jira/browse/YARN-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168928#comment-14168928 ] Hadoop QA commented on YARN-2674: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Updated] (YARN-2669) FairScheduler: queueName shouldn't allow periods the allocation.xml

[ https://issues.apache.org/jira/browse/YARN-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2669: -- Summary: FairScheduler: queueName shouldn't allow periods the allocation.xml (was: FairScheduler: print out a wa

[jira] [Updated] (YARN-2669) FairScheduler: print out a warning log when users provider a queueName starting with "root." in the allocation.xml

[ https://issues.apache.org/jira/browse/YARN-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2669: -- Attachment: YARN-2669-1.patch > FairScheduler: print out a warning log when users provider a queueName > startin

[jira] [Commented] (YARN-2641) improve node decommission latency in RM.

[ https://issues.apache.org/jira/browse/YARN-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168767#comment-14168767 ] Hadoop QA commented on YARN-2641: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Commented] (YARN-2641) improve node decommission latency in RM.

[ https://issues.apache.org/jira/browse/YARN-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168743#comment-14168743 ] zhihai xu commented on YARN-2641: - I attached a new patch YARN-2641.002.patch which add com

[jira] [Updated] (YARN-2641) improve node decommission latency in RM.

[ https://issues.apache.org/jira/browse/YARN-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2641: Attachment: YARN-2641.002.patch > improve node decommission latency in RM. >

[jira] [Commented] (YARN-2668) yarn-registry JAR won't link against ZK 3.4.5

[ https://issues.apache.org/jira/browse/YARN-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168675#comment-14168675 ] Hudson commented on YARN-2668: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1924 (See [htt

[jira] [Commented] (YARN-1879) Mark Idempotent/AtMostOnce annotations to ApplicationMasterProtocol for RM fail over

[ https://issues.apache.org/jira/browse/YARN-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168671#comment-14168671 ] Tsuyoshi OZAWA commented on YARN-1879: -- The test faliure of TestAMRestart looks not re

[jira] [Commented] (YARN-2668) yarn-registry JAR won't link against ZK 3.4.5

[ https://issues.apache.org/jira/browse/YARN-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168661#comment-14168661 ] Hudson commented on YARN-2668: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1899 (See [https://

[jira] [Commented] (YARN-2668) yarn-registry JAR won't link against ZK 3.4.5

[ https://issues.apache.org/jira/browse/YARN-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168612#comment-14168612 ] Hudson commented on YARN-2668: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #709 (See [https://b

[jira] [Commented] (YARN-2641) improve node decommission latency in RM.

[ https://issues.apache.org/jira/browse/YARN-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168564#comment-14168564 ] zhihai xu commented on YARN-2641: - [~kasha] thanks to review the patch. Just synchronized h

[jira] [Commented] (YARN-2566) IOException happen in startLocalizer of DefaultContainerExecutor due to not enough disk space for the first localDir.

[ https://issues.apache.org/jira/browse/YARN-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168546#comment-14168546 ] zhihai xu commented on YARN-2566: - [~kasha], thanks for finding the compilation error. I at

[jira] [Updated] (YARN-2566) IOException happen in startLocalizer of DefaultContainerExecutor due to not enough disk space for the first localDir.

[ https://issues.apache.org/jira/browse/YARN-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2566: Attachment: YARN-2566.008.patch > IOException happen in startLocalizer of DefaultContainerExecutor due to not