[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=13632630#comment-13632630 ] Chris Douglas commented on YARN-45: --- bq. ResourceRequest is not actionable in the sense

[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.6.patch Thank @Bikas for your investigation. I've modified the code. The newest patch

[jira] [Updated] (YARN-541) getAllocatedContainers() is not returning all the allocated containers

[ https://issues.apache.org/jira/browse/YARN-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krishna Kishore Bonagiri updated YARN-541: -- Attachment: yarn-dsadm-resourcemanager-isredeng.out

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

[jira] [Commented] (YARN-547) Race condition in Public / Private Localizer may result into resource getting downloaded again

of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12578902/yarn-547-20130416.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 include 3

[jira] [Updated] (YARN-547) Race condition in Public / Private Localizer may result into resource getting downloaded again

: Sub-task Reporter: Omkar Vinit Joshi Assignee: Omkar Vinit Joshi Attachments: yarn-547-20130411.1.patch, yarn-547-20130411.patch, yarn-547-20130412.patch, yarn-547-20130415.patch, yarn-547-20130416.1.patch, yarn-547-20130416.patch Public Localizer : At present

[jira] [Commented] (YARN-547) Race condition in Public / Private Localizer may result into resource getting downloaded again

-20130411.1.patch, yarn-547-20130411.patch, yarn-547-20130412.patch, yarn-547-20130415.patch, yarn-547-20130416.1.patch, yarn-547-20130416.patch Public Localizer : At present when multiple containers try to request a localized resource * If the resource is not present then first it is created

[jira] [Reopened] (YARN-501) Application Master getting killed randomly reporting excess usage of memory

[ https://issues.apache.org/jira/browse/YARN-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krishna Kishore Bonagiri reopened YARN-501: --- Added information dated 24th March, and 15th April. Please see above. As

[jira] [Commented] (YARN-444) Move special container exit codes from YarnConfiguration to API

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

[jira] [Commented] (YARN-580) Delay scheduling in capacity scheduler is not ensuring 100% locality

[ https://issues.apache.org/jira/browse/YARN-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632830#comment-13632830 ] Thomas Graves commented on YARN-580: Depending on what version you are using

[jira] [Commented] (YARN-444) Move special container exit codes from YarnConfiguration to API

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

[jira] [Commented] (YARN-168) No way to turn off virtual memory limits without turning off physical memory limits

[ https://issues.apache.org/jira/browse/YARN-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632868#comment-13632868 ] Krishna Kishore Bonagiri commented on YARN-168: --- How can I get this fix if I

[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=13632975#comment-13632975 ] Bikas Saha commented on YARN-514: - StartAppAttemptTransition and

[jira] [Commented] (YARN-579) Make ApplicationToken part of Container's token list to help RM-restart

[ https://issues.apache.org/jira/browse/YARN-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632992#comment-13632992 ] Bikas Saha commented on YARN-579: - In order to help restart, creation of appToken needs to

[jira] [Created] (YARN-582) Restore appToken and clientToken for app attempt after RM restart

Bikas Saha created YARN-582: --- Summary: Restore appToken and clientToken for app attempt after RM restart Key: YARN-582 URL: https://issues.apache.org/jira/browse/YARN-582 Project: Hadoop YARN

[jira] [Created] (YARN-581) Test and verify that app delegation tokens are restored after RM restart

Bikas Saha created YARN-581: --- Summary: Test and verify that app delegation tokens are restored after RM restart Key: YARN-581 URL: https://issues.apache.org/jira/browse/YARN-581 Project: Hadoop YARN

[jira] [Commented] (YARN-501) Application Master getting killed randomly reporting excess usage of memory

[ https://issues.apache.org/jira/browse/YARN-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633064#comment-13633064 ] Hitesh Shah commented on YARN-501: -- @Kishore, thanks for the logs. Looking at them. Would

[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=13633072#comment-13633072 ] Bikas Saha commented on YARN-514: - I am thinking of the following RMAppManager.recover can

[jira] [Updated] (YARN-499) On container failure, surface logs to client

[ https://issues.apache.org/jira/browse/YARN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-499: Summary: On container failure, surface logs to client (was: On container failure, include last n lines of

[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: - Attachment: YARN-562.3.patch change container_allocation_timestamp to cluster_timestamp NM

[jira] [Commented] (YARN-168) No way to turn off virtual memory limits without turning off physical memory limits

[ https://issues.apache.org/jira/browse/YARN-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633110#comment-13633110 ] Hitesh Shah commented on YARN-168: -- As started in YARN-470, this is fixed for 2.0.4-alpha.

[jira] [Updated] (YARN-560) If AM fails due to overrunning resource limits, error not visible through UI sometimes

[ https://issues.apache.org/jira/browse/YARN-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-560: -- Attachment: YARN-560.patch Attaching a patch for trunk and branch-2. Doesn't apply cleanly to

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

[jira] [Commented] (YARN-560) If AM fails due to overrunning resource limits, error not visible through UI sometimes

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

[jira] [Commented] (YARN-560) If AM fails due to overrunning resource limits, error not visible through UI sometimes

[ https://issues.apache.org/jira/browse/YARN-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633183#comment-13633183 ] Sandy Ryza commented on YARN-560: - Ravi, The patch looks good to me. Nit: can you use

[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=13633194#comment-13633194 ] Karthik Kambatla commented on YARN-562: --- Hey Jian, cluster_timestamp makes me think of

[jira] [Updated] (YARN-560) If AM fails due to overrunning resource limits, error not visible through UI sometimes

[ https://issues.apache.org/jira/browse/YARN-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-560: -- Attachment: YARN-560.patch Thanks for your review Sandy. This patch uses the block comment

[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=13633219#comment-13633219 ] Vinod Kumar Vavilapalli commented on YARN-562: -- bq. Hey Jian, cluster_timestamp

[jira] [Commented] (YARN-560) If AM fails due to overrunning resource limits, error not visible through UI sometimes

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

[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=13633256#comment-13633256 ] Karthik Kambatla commented on YARN-562: --- rm_start_timestamp makes absolute sense.

[jira] [Created] (YARN-583) Application cache files should be localized under local-dir/usercache/userid/appcache/appid/filecache

Omkar Vinit Joshi created YARN-583: -- Summary: Application cache files should be localized under local-dir/usercache/userid/appcache/appid/filecache Key: YARN-583 URL:

[jira] [Assigned] (YARN-583) Application cache files should be localized under local-dir/usercache/userid/appcache/appid/filecache

[ https://issues.apache.org/jira/browse/YARN-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-583: -- Assignee: Omkar Vinit Joshi Application cache files should be localized under

[jira] [Commented] (YARN-583) Application cache files should be localized under local-dir/usercache/userid/appcache/appid/filecache

[ https://issues.apache.org/jira/browse/YARN-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633340#comment-13633340 ] Omkar Vinit Joshi commented on YARN-583: Making sure application specific cache

[jira] [Updated] (YARN-583) Application cache files should be localized under local-dir/usercache/userid/appcache/appid/filecache

[ https://issues.apache.org/jira/browse/YARN-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-583: --- Attachment: yarn-583-20130416.patch No tests to test it Application cache

[jira] [Commented] (YARN-583) Application cache files should be localized under local-dir/usercache/userid/appcache/appid/filecache

of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12579013/yarn-583-20130416.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear

[jira] [Commented] (YARN-583) Application cache files should be localized under local-dir/usercache/userid/appcache/appid/filecache

Assignee: Omkar Vinit Joshi Attachments: yarn-583-20130416.patch Currently application cache files are getting localized under local-dir/usercache/userid/appcache/appid/. however they should be localized under filecache sub directory. -- This message is automatically

[jira] [Updated] (YARN-126) yarn rmadmin help message contains reference to hadoop cli and JT

[ https://issues.apache.org/jira/browse/YARN-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rémy SAISSY updated YARN-126: - Attachment: YARN-126.patch Patch with a GNU Readline based implementation of RMAdmin.java.

[jira] [Commented] (YARN-126) yarn rmadmin help message contains reference to hadoop cli and JT

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

[jira] [Commented] (YARN-583) Application cache files should be localized under local-dir/usercache/userid/appcache/appid/filecache

/jira/browse/YARN-583 Project: Hadoop YARN Issue Type: Bug Reporter: Omkar Vinit Joshi Assignee: Omkar Vinit Joshi Attachments: yarn-583-20130416.patch Currently application cache files are getting localized under local-dir/usercache/userid

[jira] [Commented] (YARN-583) Application cache files should be localized under local-dir/usercache/userid/appcache/appid/filecache

/browse/YARN-583 Project: Hadoop YARN Issue Type: Bug Reporter: Omkar Vinit Joshi Assignee: Omkar Vinit Joshi Attachments: yarn-583-20130416.1.patch, yarn-583-20130416.patch Currently application cache files are getting localized under

[jira] [Updated] (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:all-tabpanel ] Jian He updated YARN-534: - Attachment: YARN-534.5.patch Address last comments. DEFAULT_RM_AM_MAX_ATTEMPTS is already overridden as 5 in the

[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=13633574#comment-13633574 ] Jian He commented on YARN-534: -- new patch add comments in case of work-preserve restart and put

[jira] [Created] (YARN-584) In fair scheduler web UI, queues unexpand on refresh

Sandy Ryza created YARN-584: --- Summary: In fair scheduler web UI, queues unexpand on refresh Key: YARN-584 URL: https://issues.apache.org/jira/browse/YARN-584 Project: Hadoop YARN Issue Type: Bug

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

[jira] [Commented] (YARN-500) ResourceManager webapp is using next port if configured port is already in use

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

[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 ] Xuan Gong updated YARN-561: --- Attachment: YARN-561.2.patch Remove the duplicate in ApplicationConstants Nodemanager should

[jira] [Updated] (YARN-493) NodeManager job control logic flaws on Windows

[ https://issues.apache.org/jira/browse/YARN-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated YARN-493: --- Attachment: YARN-493.4.patch Attaching rebased patch and resubmitting to Jenkins.

[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=13633739#comment-13633739 ] Vinod Kumar Vavilapalli commented on YARN-534: -- Jian/Bikas, can we open a new

[jira] [Commented] (YARN-571) User should not be part of ContainerLaunchContext

[ https://issues.apache.org/jira/browse/YARN-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633743#comment-13633743 ] Chris Nauroth commented on YARN-571: This patch conflicts with the patch pending on

[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 ] Xuan Gong updated YARN-561: --- Attachment: YARN-561.3.patch Fix the test case failures Nodemanager should set some key

[jira] [Commented] (YARN-500) ResourceManager webapp is using next port if configured port is already in use

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

[jira] [Commented] (YARN-493) NodeManager job control logic flaws on Windows

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

[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=13633788#comment-13633788 ] Xuan Gong commented on YARN-441: 1.Replace all occurrences of get*().put() and

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

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

[jira] [Commented] (YARN-580) Delay scheduling in capacity scheduler is not ensuring 100% locality

[ https://issues.apache.org/jira/browse/YARN-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633807#comment-13633807 ] Devaraj K commented on YARN-580: As per my observation for this issue, when we configure