[jira] [Updated] (YARN-564) Job history logs do not log anything when JVM fails to start

[ https://issues.apache.org/jira/browse/YARN-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated YARN-564: - Attachment: yarn-error.png Screenshot of JHS UI > Job history logs do not log anything when JVM fa

[jira] [Created] (YARN-564) Job history logs do not log anything when JVM fails to start

Gopal V created YARN-564: Summary: Job history logs do not log anything when JVM fails to start Key: YARN-564 URL: https://issues.apache.org/jira/browse/YARN-564 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-565) AM UI does not show splits/locality info

Gopal V created YARN-565: Summary: AM UI does not show splits/locality info Key: YARN-565 URL: https://issues.apache.org/jira/browse/YARN-565 Project: Hadoop YARN Issue Type: Improvement

[jira] [Created] (YARN-566) Add a misconfiguration diagnostic or highlight mismatched resource.mb vs -Xmx

Gopal V created YARN-566: Summary: Add a misconfiguration diagnostic or highlight mismatched resource.mb vs -Xmx Key: YARN-566 URL: https://issues.apache.org/jira/browse/YARN-566 Project: Hadoop YARN

[jira] [Updated] (YARN-566) Add a misconfiguration diagnostic or highlight mismatched resource.mb vs -Xmx

[ https://issues.apache.org/jira/browse/YARN-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated YARN-566: - Labels: usability (was: ) > Add a misconfiguration diagnostic or highlight mismatched resource.mb vs -Xmx > --

[jira] [Commented] (YARN-495) Change NM behavior of reboot to resync

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

[jira] [Commented] (YARN-539) LocalizedResources are leaked in memory in case resource localization fails

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

[jira] [Commented] (YARN-487) TestDiskFailures fails on Windows due to path mishandling

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

[jira] [Updated] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

[ https://issues.apache.org/jira/browse/YARN-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Gorshkov updated YARN-427: -- Attachment: YARN-427-trunk-b.patch > Coverage fix for org.apache.hadoop.yarn.server.api.* > -

[jira] [Updated] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

[ https://issues.apache.org/jira/browse/YARN-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Gorshkov updated YARN-427: -- Attachment: YARN-427-branch-2-b.patch > Coverage fix for org.apache.hadoop.yarn.server.api.*

[jira] [Updated] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

[ https://issues.apache.org/jira/browse/YARN-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Gorshkov updated YARN-427: -- Attachment: (was: YARN-427-branch-2-b.patch) > Coverage fix for org.apache.hadoop.yarn.se

[jira] [Updated] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

[ https://issues.apache.org/jira/browse/YARN-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Gorshkov updated YARN-427: -- Attachment: (was: YARN-427-trunk-b.patch) > Coverage fix for org.apache.hadoop.yarn.serve

[jira] [Commented] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

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

[jira] [Updated] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

[ https://issues.apache.org/jira/browse/YARN-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Gorshkov updated YARN-427: -- Attachment: YARN-427-branch-2-b.patch YARN-427-branch-0.23-b.patch > Coverage

[jira] [Updated] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

[ https://issues.apache.org/jira/browse/YARN-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Gorshkov updated YARN-427: -- Attachment: YARN-427-trunk-b.patch > Coverage fix for org.apache.hadoop.yarn.server.api.* > -

[jira] [Commented] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

[ https://issues.apache.org/jira/browse/YARN-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628860#comment-13628860 ] Aleksey Gorshkov commented on YARN-427: --- Patches updated patch YARN-427-trunk-b.patch

[jira] [Commented] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

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

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628889#comment-13628889 ] Alejandro Abdelnur commented on YARN-45: Carlo, what about a small twist? A preempt

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628893#comment-13628893 ] Alejandro Abdelnur commented on YARN-45: Forgot to add, unless I'm missing something

[jira] [Commented] (YARN-539) LocalizedResources are leaked in memory in case resource localization fails

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

[jira] [Commented] (YARN-495) Change NM behavior of reboot to resync

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

[jira] [Commented] (YARN-487) TestDiskFailures fails on Windows due to path mishandling

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

[jira] [Created] (YARN-567) RM changes to support preemption for FairScheduler and CapacityScheduler

Carlo Curino created YARN-567: - Summary: RM changes to support preemption for FairScheduler and CapacityScheduler Key: YARN-567 URL: https://issues.apache.org/jira/browse/YARN-567 Project: Hadoop YARN

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628922#comment-13628922 ] Carlo Curino commented on YARN-45: -- Our main focus for now is to rebalance capacity, in this

[jira] [Created] (YARN-568) FairScheduler: support for work-preserving preemption

Carlo Curino created YARN-568: - Summary: FairScheduler: support for work-preserving preemption Key: YARN-568 URL: https://issues.apache.org/jira/browse/YARN-568 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-569) CapacityScheduler: support for preemption (using a capacity monitor)

Carlo Curino created YARN-569: - Summary: CapacityScheduler: support for preemption (using a capacity monitor) Key: YARN-569 URL: https://issues.apache.org/jira/browse/YARN-569 Project: Hadoop YARN

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628930#comment-13628930 ] Carlo Curino commented on YARN-45: -- Sorry I read only your last comment and answered to that

[jira] [Updated] (YARN-567) RM changes to support preemption for FairScheduler and CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-567: -- Description: A common tradeoff in scheduling jobs is between keeping the cluster busy and enforcing capa

[jira] [Updated] (YARN-568) FairScheduler: support for work-preserving preemption

[ https://issues.apache.org/jira/browse/YARN-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-568: -- Description: In the attached patch, we modified the FairScheduler to substitute its preemption-by-killl

[jira] [Updated] (YARN-569) CapacityScheduler: support for preemption (using a capacity monitor)

[ https://issues.apache.org/jira/browse/YARN-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-569: -- Description: There is a tension between the fast-pace reactive role of the CapacityScheduler, which need

[jira] [Updated] (YARN-567) RM changes to support preemption for FairScheduler and CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-567: -- Attachment: common.patch > RM changes to support preemption for FairScheduler and CapacityScheduler >

[jira] [Updated] (YARN-568) FairScheduler: support for work-preserving preemption

[ https://issues.apache.org/jira/browse/YARN-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-568: -- Attachment: fair.patch > FairScheduler: support for work-preserving preemption > ---

[jira] [Updated] (YARN-569) CapacityScheduler: support for preemption (using a capacity monitor)

[ https://issues.apache.org/jira/browse/YARN-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-569: -- Attachment: capacity.patch > CapacityScheduler: support for preemption (using a capacity monitor) > -

[jira] [Updated] (YARN-569) CapacityScheduler: support for preemption (using a capacity monitor)

[ https://issues.apache.org/jira/browse/YARN-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-569: -- Attachment: 3queues.pdf CapScheduler_with_preemption.pdf > CapacityScheduler: support

[jira] [Commented] (YARN-569) CapacityScheduler: support for preemption (using a capacity monitor)

[ https://issues.apache.org/jira/browse/YARN-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628937#comment-13628937 ] Carlo Curino commented on YARN-569: --- - Comments of attached Graphs --

[jira] [Updated] (YARN-568) FairScheduler: support for work-preserving preemption

[ https://issues.apache.org/jira/browse/YARN-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-568: -- Assignee: Carlo Curino > FairScheduler: support for work-preserving preemption > ---

[jira] [Updated] (YARN-569) CapacityScheduler: support for preemption (using a capacity monitor)

[ https://issues.apache.org/jira/browse/YARN-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-569: -- Assignee: Carlo Curino > CapacityScheduler: support for preemption (using a capacity monitor) > -

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628938#comment-13628938 ] Alejandro Abdelnur commented on YARN-45: I'm just trying to see if we can have (at le

[jira] [Commented] (YARN-495) Change NM behavior of reboot to resync

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

[jira] [Commented] (YARN-487) TestDiskFailures fails on Windows due to path mishandling

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

[jira] [Commented] (YARN-539) LocalizedResources are leaked in memory in case resource localization fails

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

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628950#comment-13628950 ] Carlo Curino commented on YARN-45: -- Agreed on a single message, where the semantics is: 1) i

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629070#comment-13629070 ] Alejandro Abdelnur commented on YARN-45: sounds good > Scheduler fee

[jira] [Updated] (YARN-563) Add application type to ApplicationReport

[ https://issues.apache.org/jira/browse/YARN-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-563: Issue Type: Sub-task (was: Improvement) Parent: YARN-386 > Add application type to ApplicationRe

[jira] [Commented] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state

[ https://issues.apache.org/jira/browse/YARN-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629147#comment-13629147 ] Omkar Vinit Joshi commented on YARN-547: There are couple of invalid transition for

[jira] [Assigned] (YARN-559) Make all YARN API and libraries available through an api jar

[ https://issues.apache.org/jira/browse/YARN-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy reassigned YARN-559: -- Assignee: Vinod Kumar Vavilapalli > Make all YARN API and libraries available through an api

[jira] [Commented] (YARN-457) Setting updated nodes from null to null causes NPE in AllocateResponsePBImpl

[ https://issues.apache.org/jira/browse/YARN-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629231#comment-13629231 ] Xuan Gong commented on YARN-457: First of all, I think the changes will be AllocationRespons

[jira] [Commented] (YARN-486) Change startContainer NM API to accept Container as a parameter and make ContainerLaunchContext user land

[ https://issues.apache.org/jira/browse/YARN-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629256#comment-13629256 ] Vinod Kumar Vavilapalli commented on YARN-486: -- I committed this to trunk, it i

[jira] [Commented] (YARN-486) Change startContainer NM API to accept Container as a parameter and make ContainerLaunchContext user land

[ https://issues.apache.org/jira/browse/YARN-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629265#comment-13629265 ] Hudson commented on YARN-486: - Integrated in Hadoop-trunk-Commit #3596 (See [https://builds.apa

[jira] [Commented] (YARN-563) Add application type to ApplicationReport

[ https://issues.apache.org/jira/browse/YARN-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629204#comment-13629204 ] Hitesh Shah commented on YARN-563: -- +1 on the suggestion. If you are working on this, a few

[jira] [Updated] (YARN-542) Change the default global AM max-attempts value to be not one

[ https://issues.apache.org/jira/browse/YARN-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-542: - Description: Today, the global AM max-attempts is set to 1 which is a bad choice. AM max-attempts accounts

[jira] [Updated] (YARN-542) Change the default global AM max-attempts value to be not one

[ https://issues.apache.org/jira/browse/YARN-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-542: - Summary: Change the default global AM max-attempts value to be not one (was: Change the default AM retry v

[jira] [Commented] (YARN-486) Change startContainer NM API to accept Container as a parameter and make ContainerLaunchContext user land

[ https://issues.apache.org/jira/browse/YARN-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629335#comment-13629335 ] Xuan Gong commented on YARN-486: Can not merge into branch-2, because There is no such test

[jira] [Commented] (YARN-441) Clean up unused collection methods in various APIs

[ https://issues.apache.org/jira/browse/YARN-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629377#comment-13629377 ] Xuan Gong commented on YARN-441: Add the void setServiceResponse(String key, ByteBuffer valu

[jira] [Updated] (YARN-441) Clean up unused collection methods in various APIs

[ https://issues.apache.org/jira/browse/YARN-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-441: --- Attachment: YARN-441.3.patch > Clean up unused collection methods in various APIs > ---

[jira] [Commented] (YARN-441) Clean up unused collection methods in various APIs

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

[jira] [Updated] (YARN-542) Change the default global AM max-attempts value to be not one

[ https://issues.apache.org/jira/browse/YARN-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-542: - Attachment: YARN-542.1.patch I've drafted a patch, which includes the following modifications: 1. Change t

[jira] [Updated] (YARN-319) Submit a job to a queue that not allowed in fairScheduler, client will hold forever.

[ https://issues.apache.org/jira/browse/YARN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-319: - Fix Version/s: (was: 2.0.3-alpha) 2.0.5-beta Even though the

[jira] [Commented] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state

[ https://issues.apache.org/jira/browse/YARN-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629467#comment-13629467 ] Omkar Vinit Joshi commented on YARN-547: Fix details :- * Underlying problem:- Resou

[jira] [Updated] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state

[ https://issues.apache.org/jira/browse/YARN-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-547: --- Attachment: yarn-547-20130411.patch > New resource localization is tried even w

[jira] [Commented] (YARN-486) Change startContainer NM API to accept Container as a parameter and make ContainerLaunchContext user land

[ https://issues.apache.org/jira/browse/YARN-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629475#comment-13629475 ] Xuan Gong commented on YARN-486: Another issue is at YARN-488 which is not committed into br

[jira] [Commented] (YARN-486) Change startContainer NM API to accept Container as a parameter and make ContainerLaunchContext user land

[ https://issues.apache.org/jira/browse/YARN-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629476#comment-13629476 ] Vinod Kumar Vavilapalli commented on YARN-486: -- I merged YARN-319 into branch-2

[jira] [Commented] (YARN-542) Change the default global AM max-attempts value to be not one

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

[jira] [Resolved] (YARN-537) Waiting containers are not informed if private localization for a resource fails.

[ https://issues.apache.org/jira/browse/YARN-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-537. -- Resolution: Duplicate Fixed as part of YARN-539. Closing as duplicate.

[jira] [Resolved] (YARN-544) Failed resource localization might introduce a race condition.

[ https://issues.apache.org/jira/browse/YARN-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-544. -- Resolution: Duplicate Thanks for the update, Omkar. Closing this as duplicate.

[jira] [Commented] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state

s of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12578295/yarn-547-20130411.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to inclu

[jira] [Updated] (YARN-486) Change startContainer NM API to accept Container as a parameter and make ContainerLaunchContext user land

[ https://issues.apache.org/jira/browse/YARN-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-486: --- Attachment: YARN-486.6.branch2.patch Patch for branch-2 > Change startContainer NM API to acce

[jira] [Commented] (YARN-486) Change startContainer NM API to accept Container as a parameter and make ContainerLaunchContext user land

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

[jira] [Commented] (YARN-319) Submit a job to a queue that not allowed in fairScheduler, client will hold forever.

[ https://issues.apache.org/jira/browse/YARN-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629549#comment-13629549 ] Hudson commented on YARN-319: - Integrated in Hadoop-trunk-Commit #3603 (See [https://builds.apa

[jira] [Commented] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state

URL: https://issues.apache.org/jira/browse/YARN-547 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Omkar Vinit Joshi >Assignee: Omkar Vinit Joshi > Attachments: yarn-547-20130411.1.patch, yarn-547-20130411.patch > >

[jira] [Updated] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state

Issue Type: Sub-task >Reporter: Omkar Vinit Joshi >Assignee: Omkar Vinit Joshi > Attachments: yarn-547-20130411.1.patch, yarn-547-20130411.patch > > > At present when multiple containers try to request a localized resource > 1) If the res

[jira] [Updated] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state

YARN > Issue Type: Sub-task >Reporter: Omkar Vinit Joshi >Assignee: Omkar Vinit Joshi > Attachments: yarn-547-20130411.1.patch, yarn-547-20130411.patch > > > At present when multiple containers try to request a localized resource > 1) If

[jira] [Updated] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state

Issue Type: Sub-task >Reporter: Omkar Vinit Joshi >Assignee: Omkar Vinit Joshi > Attachments: yarn-547-20130411.1.patch, yarn-547-20130411.patch > > > At present when multiple containers try to request a localized resource > 1) If the res

[jira] [Commented] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state

hi > Attachments: yarn-547-20130411.1.patch, yarn-547-20130411.patch > > > At present when multiple containers try to request a localized resource > 1) If the resource is not present then first it is created and Resource > Localization starts ( LocalizedResource is in D

[jira] [Updated] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-45: --- Issue Type: Sub-task (was: Improvement) Parent: YARN-386 > Scheduler feedback to AM to release cont

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629620#comment-13629620 ] Bikas Saha commented on YARN-45: All API changes at this point are being tracked under YARN-3

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629635#comment-13629635 ] Karthik Kambatla commented on YARN-45: -- Great discussion, glad to see this coming along

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629638#comment-13629638 ] Karthik Kambatla commented on YARN-45: -- [~bikassaha], shouldn't this be under YARN-397?

[jira] [Updated] (YARN-567) RM changes to support preemption for FairScheduler and CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-567: -- Issue Type: Sub-task (was: Improvement) Parent: YARN-397 > RM changes to support preemption

[jira] [Updated] (YARN-568) FairScheduler: support for work-preserving preemption

[ https://issues.apache.org/jira/browse/YARN-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-568: -- Issue Type: Sub-task (was: Improvement) Parent: YARN-397 > FairScheduler: support for work-p

[jira] [Updated] (YARN-569) CapacityScheduler: support for preemption (using a capacity monitor)

[ https://issues.apache.org/jira/browse/YARN-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-569: -- Issue Type: Sub-task (was: Improvement) Parent: YARN-397 > CapacityScheduler: support for pr

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629660#comment-13629660 ] Carlo Curino commented on YARN-45: -- [~kkambatl], yes ResourceRequests can be used to capture

[jira] [Updated] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-45: --- Issue Type: Improvement (was: Sub-task) Parent: (was: YARN-386) > Scheduler feedback to AM to r

[jira] [Updated] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-45: --- Issue Type: Sub-task (was: Improvement) Parent: YARN-397 > Scheduler feedback to AM to release cont

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629662#comment-13629662 ] Bikas Saha commented on YARN-45: Moved to sub-task of YARN-397 for scheduler API changes.

[jira] [Updated] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-45: - Attachment: YARN-45.patch > Scheduler feedback to AM to release containers > ---

[jira] [Updated] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-45: - Attachment: (was: YARN-45.patch) > Scheduler feedback to AM to release containers >

[jira] [Updated] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-45: - Attachment: YARN-45.patch > Scheduler feedback to AM to release containers > ---

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

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

[jira] [Updated] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-45: - Attachment: (was: YARN-45.patch) > Scheduler feedback to AM to release containers >

[jira] [Updated] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlo Curino updated YARN-45: - Attachment: YARN-45.patch > Scheduler feedback to AM to release containers > ---

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

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

[jira] [Updated] (YARN-482) FS: Extend SchedulingMode to intermediate queues

[ https://issues.apache.org/jira/browse/YARN-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-482: -- Attachment: yarn-482.patch Here is a preliminary patch that # Renames SchedulingMode to Schedulin

[jira] [Commented] (YARN-514) Delayed store operations should not result in RM unavailability for app submission

[ https://issues.apache.org/jira/browse/YARN-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629742#comment-13629742 ] Bikas Saha commented on YARN-514: - Looks good overall. Minor tab issues in the patch. I don

[jira] [Commented] (YARN-514) Delayed store operations should not result in RM unavailability for app submission

[ https://issues.apache.org/jira/browse/YARN-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629745#comment-13629745 ] Bikas Saha commented on YARN-514: - For MAPREDUCE-5140 please check for uses of both NEW and

[jira] [Commented] (YARN-514) Delayed store operations should not result in RM unavailability for app submission

[ https://issues.apache.org/jira/browse/YARN-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629782#comment-13629782 ] Zhijie Shen commented on YARN-514: -- @Biksa, the enum values in the proto needs to be change

[jira] [Updated] (YARN-514) Delayed store operations should not result in RM unavailability for app submission

[ https://issues.apache.org/jira/browse/YARN-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-514: - Attachment: YARN-514.4.patch Fix the incorrect indents. > Delayed store operations should

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629806#comment-13629806 ] Carlo Curino commented on YARN-45: -- Note: we don't have tests as there are no tests for the

[jira] [Commented] (YARN-441) Clean up unused collection methods in various APIs

[ https://issues.apache.org/jira/browse/YARN-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629819#comment-13629819 ] Xuan Gong commented on YARN-441: Patch3 self Review: 1. For each record API, we should only

[jira] [Commented] (YARN-514) Delayed store operations should not result in RM unavailability for app submission

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

  1   2   >