[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.2.patch Update TestRMAppTransitions to avoid the bug of determining the transit

[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-tabpanelfocusedCommentId=13627572#comment-13627572 ] Hadoop QA commented on YARN-514: {color:green}+1 overall{color}. Here are the results of

[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-tabpanelfocusedCommentId=13627664#comment-13627664 ] Xuan Gong commented on YARN-486: bq:ApplicationSubmissionContext: We SHOULD NOT add Resource

[jira] [Commented] (YARN-112) Race in localization can cause containers to fail

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

[jira] [Commented] (YARN-534) AM max attempts is not checked when RM restart and try to recover attempts

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

[jira] [Commented] (YARN-117) Enhance YARN service model

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

[jira] [Commented] (YARN-112) Race in localization can cause containers to fail

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

[jira] [Commented] (YARN-534) AM max attempts is not checked when RM restart and try to recover attempts

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

[jira] [Commented] (YARN-112) Race in localization can cause containers to fail

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

[jira] [Commented] (YARN-534) AM max attempts is not checked when RM restart and try to recover attempts

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

[jira] [Updated] (YARN-561) Nodemanager should set some key information into the environment of every container that it launches.

[ https://issues.apache.org/jira/browse/YARN-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-561: Assignee: Omkar Vinit Joshi Nodemanager should set some key information into the environment of every

[jira] [Commented] (YARN-534) AM max attempts is not checked when RM restart and try to recover attempts

[ https://issues.apache.org/jira/browse/YARN-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13628015#comment-13628015 ] Bikas Saha commented on YARN-534: - There needs to be a comment here that this logic needs to

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

[ https://issues.apache.org/jira/browse/YARN-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13628019#comment-13628019 ] Zhijie Shen commented on YARN-542: -- @Vinod , how about conservatively changing max attempts

[jira] [Created] (YARN-562) AM should reject containers allocated by previous RM

Jian He created YARN-562: Summary: AM should reject containers allocated by previous RM Key: YARN-562 URL: https://issues.apache.org/jira/browse/YARN-562 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-276) Capacity Scheduler can hang when submit many jobs concurrently

[ https://issues.apache.org/jira/browse/YARN-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13628069#comment-13628069 ] Zhijie Shen commented on YARN-276: -- I found one more issue with the per queue basis check.

[jira] [Updated] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-562: - Summary: NM should reject containers allocated by previous RM (was: AM should reject containers allocated by

[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-tabpanelfocusedCommentId=13628245#comment-13628245 ] Vinod Kumar Vavilapalli commented on YARN-495: -- Looked at the latest patch.

[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-tabpanelfocusedCommentId=13628247#comment-13628247 ] Alejandro Abdelnur commented on YARN-45: Nice, the proposed functionality comes quite

[jira] [Commented] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13628250#comment-13628250 ] Vinod Kumar Vavilapalli commented on YARN-562: -- Yes, the easiest way to do this

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

[ https://issues.apache.org/jira/browse/YARN-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-495: - Attachment: YARN-495.4.patch YARN-495.4.patch fix last comments, except stopping any startContainers() in

[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-tabpanelfocusedCommentId=13628305#comment-13628305 ] Carlo Curino commented on YARN-45: -- Alejandro, thanks for the feedback, and yes you are spot

[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.5.patch New patch has several changes: 1. apply all the comments 2. Remove user from

[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-tabpanelfocusedCommentId=13628358#comment-13628358 ] Alejandro Abdelnur commented on YARN-45: Carlo, I may be missing something then.

[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.2.patch Remove two more functions from AllocateRequest: 1. addAllAsk 2. addAllRelease

[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-tabpanelfocusedCommentId=13628384#comment-13628384 ] Xuan Gong commented on YARN-457: Comments: I think if the updatedNodes == null, just simply

[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-tabpanelfocusedCommentId=13628394#comment-13628394 ] Hadoop QA commented on YARN-441: {color:green}+1 overall{color}. Here are the results of

[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-tabpanelfocusedCommentId=13628440#comment-13628440 ] Hadoop QA commented on YARN-486: {color:red}-1 overall{color}. Here are the results of

[jira] [Assigned] (YARN-542) Change the default AM retry value to be not one

[ https://issues.apache.org/jira/browse/YARN-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen reassigned YARN-542: Assignee: Zhijie Shen (was: Vinod Kumar Vavilapalli) Change the default AM retry value to be

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

Thomas Weise created YARN-563: - Summary: Add application type to ApplicationReport Key: YARN-563 URL: https://issues.apache.org/jira/browse/YARN-563 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-489) Setter of xxxxPBImpl doesn't really set the collection, but append its items to an existing collection

[ https://issues.apache.org/jira/browse/YARN-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-489: - Issue Type: Sub-task (was: Bug) Parent: YARN-386 Setter of

[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.patch Fix the test failures. Change startContainer NM API to accept

[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-tabpanelfocusedCommentId=13628503#comment-13628503 ] Alejandro Abdelnur commented on YARN-45: My soft objection to #1 is just it is

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

[ https://issues.apache.org/jira/browse/YARN-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-495: - Attachment: YARN-495.5.patch YARN-495.5.patch fix above test failure: miss break in switch shutdown case. And

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

Vinit Joshi Assignee: Omkar Vinit Joshi Attachments: yarn-539-20130410.1.patch, yarn-539-20130410.2.patch, yarn-539-20130410.patch If resource localization fails then resource remains in memory and is 1) Either cleaned up when next time cache cleanup runs and there is space

[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-tabpanelfocusedCommentId=13628528#comment-13628528 ] Hadoop QA commented on YARN-495: {color:green}+1 overall{color}. Here are the results of

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

[ https://issues.apache.org/jira/browse/YARN-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-495: - Attachment: YARN-495.6.patch fix format and name issues Change NM behavior of reboot to resync

[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-tabpanelfocusedCommentId=13628549#comment-13628549 ] Vinod Kumar Vavilapalli commented on YARN-495: -- +1, this looks good. Will check

[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-tabpanelfocusedCommentId=13628551#comment-13628551 ] Hudson commented on YARN-487: - Integrated in Hadoop-trunk-Commit #3590 (See

[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-tabpanelfocusedCommentId=13628552#comment-13628552 ] Vinod Kumar Vavilapalli commented on YARN-486: -- I am good, +1 for the latest

[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-tabpanelfocusedCommentId=13628565#comment-13628565 ] Hadoop QA commented on YARN-486: {color:green}+1 overall{color}. Here are the results of

[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-tabpanelfocusedCommentId=13628567#comment-13628567 ] Hadoop QA commented on YARN-495: {color:green}+1 overall{color}. Here are the results of

[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-tabpanelfocusedCommentId=13628582#comment-13628582 ] Hudson commented on YARN-495: - Integrated in Hadoop-trunk-Commit #3591 (See

[jira] [Commented] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13628583#comment-13628583 ] Vinod Kumar Vavilapalli commented on YARN-562: -- On YARN-495, I

[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.3.patch I've updated the patch. the major modifications are as follows: 1. SAVING is

[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 ] Vinod Kumar Vavilapalli updated YARN-486: - Attachment: YARN-486-20130410.txt This should fix it - a minor update to reflect

[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-tabpanelfocusedCommentId=13628625#comment-13628625 ] Carlo Curino commented on YARN-45: -- Agreed. As for #1, your previous comments made us

[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-tabpanelfocusedCommentId=13628649#comment-13628649 ] Hadoop QA commented on YARN-514: {color:green}+1 overall{color}. Here are the results of

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

.patch, yarn-539-20130410.2.patch, yarn-539-20130410.patch If resource localization fails then resource remains in memory and is 1) Either cleaned up when next time cache cleanup runs and there is space crunch. (If sufficient space in cache is available then it will remain in memory). 2

[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-tabpanelfocusedCommentId=13628699#comment-13628699 ] Hadoop QA commented on YARN-514: {color:green}+1 overall{color}. Here are the results of