[jira] [Commented] (YARN-2187) FairScheduler: Disable max-AM-share check by default

[ https://issues.apache.org/jira/browse/YARN-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039726#comment-14039726 ] Karthik Kambatla commented on YARN-2187: +1. Committing this. FairScheduler:

[jira] [Commented] (YARN-2187) FairScheduler: Disable max-AM-share check by default

[ https://issues.apache.org/jira/browse/YARN-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039729#comment-14039729 ] Hudson commented on YARN-2187: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5749 (See

[jira] [Commented] (YARN-1680) availableResources sent to applicationMaster in heartbeat should exclude blacklistedNodes free memory.

[ https://issues.apache.org/jira/browse/YARN-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039733#comment-14039733 ] Niels Basjes commented on YARN-1680: Looks like YARN-2105 has been fixed. Can someone

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039744#comment-14039744 ] Varun Vasudev commented on YARN-1039: - I agree with [~zjshen]. Using the tags field

[jira] [Commented] (YARN-2187) FairScheduler: Disable max-AM-share check by default

[ https://issues.apache.org/jira/browse/YARN-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039783#comment-14039783 ] Hudson commented on YARN-2187: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #590 (See

[jira] [Commented] (YARN-2187) FairScheduler: Disable max-AM-share check by default

[ https://issues.apache.org/jira/browse/YARN-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039843#comment-14039843 ] Hudson commented on YARN-2187: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1781 (See

[jira] [Commented] (YARN-2187) FairScheduler: Disable max-AM-share check by default

[ https://issues.apache.org/jira/browse/YARN-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039867#comment-14039867 ] Hudson commented on YARN-2187: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1808 (See

[jira] [Commented] (YARN-2144) Add logs when preemption occurs

[ https://issues.apache.org/jira/browse/YARN-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039934#comment-14039934 ] Carlo Curino commented on YARN-2144: I only skimmed the patch quickly, but I see

[jira] [Commented] (YARN-2190) Provide a Windows container executor that can limit memory and CPU

[ https://issues.apache.org/jira/browse/YARN-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039973#comment-14039973 ] Steve Loughran commented on YARN-2190: -- # what would the implications for the move

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14039976#comment-14039976 ] Steve Loughran commented on YARN-1039: -- # I'd make the long-lived flag a container

[jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate long lived

[ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040001#comment-14040001 ] Zhijie Shen commented on YARN-1039: --- bq. An AM may wish to indicate that some containers

[jira] [Commented] (YARN-2144) Add logs when preemption occurs

[ https://issues.apache.org/jira/browse/YARN-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040010#comment-14040010 ] Wangda Tan commented on YARN-2144: -- Since suggested by [~jianhe], to propose of this JIRA,