[jira] [Updated] (YARN-2054) Poor defaults for YARN ZK configs for retries and retry-inteval

[ https://issues.apache.org/jira/browse/YARN-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2054: --- Attachment: yarn-2054-3.patch Patch with unit test. Poor defaults for YARN ZK configs for

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010854#comment-14010854 ] Karthik Kambatla commented on YARN-2010: bq. In non-workpreserving restart, since

[jira] [Commented] (YARN-2092) Incompatible org.codehaus.jackson* dependencies when moving from 2.4.0 to 2.5.0-SNAPSHOT

[ https://issues.apache.org/jira/browse/YARN-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010906#comment-14010906 ] Steve Loughran commented on YARN-2092: -- # code using Apache Curator was one -in YARN

[jira] [Commented] (YARN-2054) Poor defaults for YARN ZK configs for retries and retry-inteval

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

[jira] [Commented] (YARN-2105) Fix TestFairScheduler after YARN-2012

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

[jira] [Commented] (YARN-2012) Fair Scheduler: allow default queue placement rule to take an arbitrary queue

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

[jira] [Commented] (YARN-2012) Fair Scheduler: allow default queue placement rule to take an arbitrary queue

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

[jira] [Commented] (YARN-2105) Fix TestFairScheduler after YARN-2012

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

[jira] [Commented] (YARN-2012) Fair Scheduler: allow default queue placement rule to take an arbitrary queue

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

[jira] [Updated] (YARN-1338) Recover localized resource cache state upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-1338: - Attachment: YARN-1338v6.patch Thanks for the additional comments, Junping. bq. Do we have any code to

[jira] [Created] (YARN-2109) TestRM fails some tests when some tests run with CapacityScheduler and some with FairScheduler

Anubhav Dhoot created YARN-2109: --- Summary: TestRM fails some tests when some tests run with CapacityScheduler and some with FairScheduler Key: YARN-2109 URL: https://issues.apache.org/jira/browse/YARN-2109

[jira] [Commented] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011320#comment-14011320 ] Tsuyoshi OZAWA commented on YARN-1474: -- Thanks Karthik for the comments. I'd like to

[jira] [Commented] (YARN-1338) Recover localized resource cache state upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011325#comment-14011325 ] Hadoop QA commented on YARN-1338: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011331#comment-14011331 ] Karthik Kambatla commented on YARN-1474: I think that is the step in the right

[jira] [Updated] (YARN-596) In fair scheduler, intra-application container priorities affect inter-application preemption decisions

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-596: - Attachment: YARN-596.patch Thanks, Sandy. Upload a new patch to fix your comments. In fair scheduler,

[jira] [Commented] (YARN-2054) Poor defaults for YARN ZK configs for retries and retry-inteval

[ https://issues.apache.org/jira/browse/YARN-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011335#comment-14011335 ] Xuan Gong commented on YARN-2054: - [~kasha] Looks like you need to update the patch. There

[jira] [Updated] (YARN-596) In fair scheduler, intra-application container priorities affect inter-application preemption decisions

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-596: - Attachment: YARN-596.patch In fair scheduler, intra-application container priorities affect inter-application

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011355#comment-14011355 ] Jian He commented on YARN-2010: --- bq. The stack trace corresponds to non-work-preserving

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011362#comment-14011362 ] Karthik Kambatla commented on YARN-2010: I see. Thanks for the input. Let me check

[jira] [Commented] (YARN-2107) Refactor timeline classes into server.timeline package

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

[jira] [Assigned] (YARN-2098) App priority support in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan reassigned YARN-2098: - Assignee: Wei Yan App priority support in Fair Scheduler --

[jira] [Created] (YARN-2110) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

Anubhav Dhoot created YARN-2110: --- Summary: TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler Key: YARN-2110 URL: https://issues.apache.org/jira/browse/YARN-2110 Project:

[jira] [Updated] (YARN-2110) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2110: Description: The TestAMRestart#testAMRestartWithExistingContainers does a cast to

[jira] [Commented] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011507#comment-14011507 ] Sandy Ryza commented on YARN-1474: -- My opinion is that it's ok to change these semantics,

[jira] [Resolved] (YARN-2068) FairScheduler uses the same ResourceCalculator for all policies

[ https://issues.apache.org/jira/browse/YARN-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza resolved YARN-2068. -- Resolution: Invalid Closing this as invalid. Obviously feel free to reopen if I'm missing something.

[jira] [Commented] (YARN-1972) Implement secure Windows Container Executor

[ https://issues.apache.org/jira/browse/YARN-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011515#comment-14011515 ] Vinod Kumar Vavilapalli commented on YARN-1972: --- Thanks for working on this

[jira] [Commented] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

[ https://issues.apache.org/jira/browse/YARN-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011523#comment-14011523 ] Sandy Ryza commented on YARN-2026: -- The nice thing about fair share currently is that it's

[jira] [Commented] (YARN-1063) Winutils needs ability to create task as domain user

[ https://issues.apache.org/jira/browse/YARN-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011524#comment-14011524 ] Vinod Kumar Vavilapalli commented on YARN-1063: --- Scanned through the patch.

[jira] [Created] (YARN-2111) In FairScheduler.attemptScheduling, we won't count containers as assigned if they have 0 memory but non-zero cores

Sandy Ryza created YARN-2111: Summary: In FairScheduler.attemptScheduling, we won't count containers as assigned if they have 0 memory but non-zero cores Key: YARN-2111 URL:

[jira] [Assigned] (YARN-2111) In FairScheduler.attemptScheduling, we won't count containers as assigned if they have 0 memory but non-zero cores

[ https://issues.apache.org/jira/browse/YARN-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza reassigned YARN-2111: Assignee: Sandy Ryza In FairScheduler.attemptScheduling, we won't count containers as assigned if

[jira] [Updated] (YARN-2111) In FairScheduler.attemptScheduling, we won't count containers as assigned if they have 0 memory but non-zero cores

[ https://issues.apache.org/jira/browse/YARN-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-2111: - Attachment: YARN-2111.patch In FairScheduler.attemptScheduling, we won't count containers as assigned if

[jira] [Commented] (YARN-596) In fair scheduler, intra-application container priorities affect inter-application preemption decisions

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011540#comment-14011540 ] Sandy Ryza commented on YARN-596: - +1 In fair scheduler, intra-application container

[jira] [Commented] (YARN-596) In fair scheduler, intra-application container priorities affect inter-application preemption decisions

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011542#comment-14011542 ] Sandy Ryza commented on YARN-596: - (pending Jenkins) In fair scheduler, intra-application

[jira] [Updated] (YARN-2098) App priority support in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2098: -- Attachment: YARN-2098.patch App priority support in Fair Scheduler --

[jira] [Assigned] (YARN-2110) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He reassigned YARN-2110: - Assignee: Chen He TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[jira] [Commented] (YARN-2110) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011571#comment-14011571 ] Chen He commented on YARN-2110: --- I will take this.

[jira] [Commented] (YARN-2109) TestRM fails some tests when some tests run with CapacityScheduler and some with FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011582#comment-14011582 ] Chen He commented on YARN-2109: --- This is interesting and I will work on it. TestRM fails

[jira] [Assigned] (YARN-2109) TestRM fails some tests when some tests run with CapacityScheduler and some with FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He reassigned YARN-2109: - Assignee: Chen He TestRM fails some tests when some tests run with CapacityScheduler and some with

[jira] [Commented] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

[ https://issues.apache.org/jira/browse/YARN-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011587#comment-14011587 ] Sandy Ryza commented on YARN-1913: -- I think we should avoid doing approximate calculation

[jira] [Commented] (YARN-1801) NPE in public localizer

[ https://issues.apache.org/jira/browse/YARN-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011601#comment-14011601 ] Jason Lowe commented on YARN-1801: -- Strictly speaking, the patch does prevent the NPE.

[jira] [Commented] (YARN-2111) In FairScheduler.attemptScheduling, we won't count containers as assigned if they have 0 memory but non-zero cores

[ https://issues.apache.org/jira/browse/YARN-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011625#comment-14011625 ] Hadoop QA commented on YARN-2111: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (YARN-2111) In FairScheduler.attemptScheduling, we don't count containers as assigned if they have 0 memory but non-zero cores

[ https://issues.apache.org/jira/browse/YARN-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-2111: - Summary: In FairScheduler.attemptScheduling, we don't count containers as assigned if they have 0 memory

[jira] [Created] (YARN-2112) Hadoop-client is missing jackson libs due to inappropriate configs in pom.xml

Zhijie Shen created YARN-2112: - Summary: Hadoop-client is missing jackson libs due to inappropriate configs in pom.xml Key: YARN-2112 URL: https://issues.apache.org/jira/browse/YARN-2112 Project: Hadoop

[jira] [Commented] (YARN-2098) App priority support in Fair Scheduler

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

[jira] [Updated] (YARN-2112) Hadoop-client is missing jackson libs due to inappropriate configs in pom.xml

[ https://issues.apache.org/jira/browse/YARN-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2112: -- Attachment: YARN-2112.1.patch Create a patch to correct the configs in pom.xml, and make sure all 4

[jira] [Updated] (YARN-2112) Hadoop-client is missing jackson libs due to inappropriate configs in pom.xml

[ https://issues.apache.org/jira/browse/YARN-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2112: -- Target Version/s: 2.5.0 Hadoop-client is missing jackson libs due to inappropriate configs in pom.xml

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011686#comment-14011686 ] Jian He commented on YARN-2010: --- I agree that failing to recover an app shouldn’t fail the

[jira] [Commented] (YARN-2112) Hadoop-client is missing jackson libs due to inappropriate configs in pom.xml

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

[jira] [Updated] (YARN-2054) Poor defaults for YARN ZK configs for retries and retry-inteval

[ https://issues.apache.org/jira/browse/YARN-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2054: --- Attachment: yarn-2054-4.patch Sorry for the bulky patch - forgot to rebase against trunk

[jira] [Updated] (YARN-2110) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-2110: -- Attachment: YARN-2110.patch TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[jira] [Commented] (YARN-2110) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011788#comment-14011788 ] Chen He commented on YARN-2110: --- change casting from CapacityScheduler to

[jira] [Updated] (YARN-2109) TestRM fails some tests when some tests run with CapacityScheduler and some with FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-2109: -- Labels: test (was: ) TestRM fails some tests when some tests run with CapacityScheduler and some with

[jira] [Updated] (YARN-2110) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-2110: -- Labels: test (was: ) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[jira] [Commented] (YARN-596) In fair scheduler, intra-application container priorities affect inter-application preemption decisions

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011807#comment-14011807 ] Ashwin Shankar commented on YARN-596: - [~ywskycn],minor comment : can you please update

[jira] [Commented] (YARN-596) In fair scheduler, intra-application container priorities affect inter-application preemption decisions

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011814#comment-14011814 ] Wei Yan commented on YARN-596: -- Thanks, [~ashwinshankar77]. I'll update a patch quickly. In

[jira] [Commented] (YARN-2054) Poor defaults for YARN ZK configs for retries and retry-inteval

[ https://issues.apache.org/jira/browse/YARN-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011818#comment-14011818 ] Hadoop QA commented on YARN-2054: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1708) Add a public API to reserve resources (part of YARN-1051)

[ https://issues.apache.org/jira/browse/YARN-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011820#comment-14011820 ] Vinod Kumar Vavilapalli commented on YARN-1708: --- Thanks for the patch

[jira] [Updated] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1474: - Attachment: YARN-1474.18.patch Thanks for sharing the opinions, Sandy and Karthik. I also think

[jira] [Commented] (YARN-2041) Hard to co-locate MR2 and Spark jobs on the same cluster in YARN

[ https://issues.apache.org/jira/browse/YARN-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011844#comment-14011844 ] Nishkam Ravi commented on YARN-2041: Unlike FIFO, whose performance deteriorates

[jira] [Updated] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

[ https://issues.apache.org/jira/browse/YARN-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Shankar updated YARN-2026: - Description: Problem1- While using hierarchical queues in fair scheduler,there are few scenarios

[jira] [Commented] (YARN-2110) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011847#comment-14011847 ] Hadoop QA commented on YARN-2110: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (YARN-596) In fair scheduler, intra-application container priorities affect inter-application preemption decisions

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-596: - Attachment: YARN-596.patch In fair scheduler, intra-application container priorities affect inter-application

[jira] [Commented] (YARN-1474) Make schedulers services

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

[jira] [Updated] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2091: - Attachment: YARN-2091.1.patch Added ContainerExitStatus.KILL_EXCEEDED_MEMORY and test to pass the

[jira] [Updated] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2010: --- Attachment: yarn-2010-3.patch New patch that gets rid of the config and addresses the issue

[jira] [Commented] (YARN-596) In fair scheduler, intra-application container priorities affect inter-application preemption decisions

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011906#comment-14011906 ] Hadoop QA commented on YARN-596: {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

[ https://issues.apache.org/jira/browse/YARN-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011907#comment-14011907 ] Ashwin Shankar commented on YARN-2026: -- Hi [~sandyr], bq. We would see that parentA is

[jira] [Commented] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

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

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011943#comment-14011943 ] Hadoop QA commented on YARN-2010: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2041) Hard to co-locate MR2 and Spark jobs on the same cluster in YARN

[ https://issues.apache.org/jira/browse/YARN-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011982#comment-14011982 ] Vinod Kumar Vavilapalli commented on YARN-2041: --- Tx for all the updates,

[jira] [Commented] (YARN-596) In fair scheduler, intra-application container priorities affect inter-application preemption decisions

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012030#comment-14012030 ] Sandy Ryza commented on YARN-596: - +1 In fair scheduler, intra-application container

[jira] [Updated] (YARN-596) Use scheduling policies throughout the hierarchy to decide which containers to preempt

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-596: Summary: Use scheduling policies throughout the hierarchy to decide which containers to preempt (was: In

[jira] [Updated] (YARN-596) Use scheduling policies throughout the queue hierarchy to decide which containers to preempt

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-596: Summary: Use scheduling policies throughout the queue hierarchy to decide which containers to preempt (was:

[jira] [Commented] (YARN-596) Use scheduling policies throughout the queue hierarchy to decide which containers to preempt

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012038#comment-14012038 ] Sandy Ryza commented on YARN-596: - I just committed this to trunk and branch-2. Thanks Wei

[jira] [Commented] (YARN-596) Use scheduling policies throughout the queue hierarchy to decide which containers to preempt

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