[jira] [Commented] (YARN-902) Used Resources field in Resourcemanager scheduler UI not displaying any values

[ https://issues.apache.org/jira/browse/YARN-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13701988#comment-13701988 ] Thomas Graves commented on YARN-902: Are you using the latest branch-2 or the released

[jira] [Updated] (YARN-347) YARN node CLI should also show CPU info as memory info in node status

[ https://issues.apache.org/jira/browse/YARN-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-347: - Issue Type: Improvement (was: Bug) YARN node CLI should also show CPU info

[jira] [Commented] (YARN-644) Basic null check is not performed on passed in arguments before using them in ContainerManagerImpl.startContainer

[ https://issues.apache.org/jira/browse/YARN-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702158#comment-13702158 ] Omkar Vinit Joshi commented on YARN-644: [~josephkniest] in these scenarios we

[jira] [Updated] (YARN-292) ResourceManager throws ArrayIndexOutOfBoundsException while handling CONTAINER_ALLOCATED for application attempt

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

[jira] [Commented] (YARN-502) RM crash with NPE on NODE_REMOVED event with FairScheduler

[ https://issues.apache.org/jira/browse/YARN-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702177#comment-13702177 ] Zhijie Shen commented on YARN-502: -- +1, the patch looks good to me RM

[jira] [Updated] (YARN-623) NodeManagers on RM web-app don't have diagnostic information

[ https://issues.apache.org/jira/browse/YARN-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-623: - Issue Type: Improvement (was: Bug) NodeManagers on RM web-app don't have

[jira] [Updated] (YARN-397) RM Scheduler api enhancements

[ https://issues.apache.org/jira/browse/YARN-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-397: - Issue Type: Improvement (was: Bug) RM Scheduler api enhancements

[jira] [Commented] (YARN-894) NodeHealthScriptRunner timeout checking is inaccurate on Windows

[ https://issues.apache.org/jira/browse/YARN-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702237#comment-13702237 ] Chris Nauroth commented on YARN-894: Hi, Chuan. This patch looks good, but I'm seeing a

[jira] [Updated] (YARN-865) RM webservices can't query on application Types

[ https://issues.apache.org/jira/browse/YARN-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-865: - Issue Type: Improvement (was: Bug) RM webservices can't query on application

[jira] [Updated] (YARN-843) TestPipeApplication should not be using AMRMToken.

[ https://issues.apache.org/jira/browse/YARN-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-843: - Issue Type: Improvement (was: Bug) TestPipeApplication should not be using

[jira] [Updated] (YARN-807) When querying apps by queue, iterating over all apps is inefficient and limiting

[ https://issues.apache.org/jira/browse/YARN-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-807: - Issue Type: Improvement (was: Bug) When querying apps by queue, iterating

[jira] [Updated] (YARN-115) yarn commands shouldn't add m to the heapsize

[ https://issues.apache.org/jira/browse/YARN-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-115: - Issue Type: Improvement (was: Bug) yarn commands shouldn't add m to the

[jira] [Updated] (YARN-148) CapacityScheduler shouldn't explicitly need YarnConfiguration

[ https://issues.apache.org/jira/browse/YARN-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-148: - Issue Type: Improvement (was: Bug) CapacityScheduler shouldn't explicitly

[jira] [Commented] (YARN-295) Resource Manager throws InvalidStateTransitonException: Invalid event: CONTAINER_FINISHED at ALLOCATED for RMAppAttemptImpl

[ https://issues.apache.org/jira/browse/YARN-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702245#comment-13702245 ] Zhijie Shen commented on YARN-295: -- I agree with moving RMAppAttempt from ALLOCATED to

[jira] [Updated] (YARN-8) Add more unit tests for CPU scheduling in CS

[ https://issues.apache.org/jira/browse/YARN-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-8: --- Issue Type: Improvement (was: Bug) Add more unit tests for CPU scheduling in CS

[jira] [Updated] (YARN-601) Refactoring the code which computes the user file cache and user application file cache paths

[ https://issues.apache.org/jira/browse/YARN-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-601: - Issue Type: Improvement (was: Bug) Refactoring the code which computes the

[jira] [Updated] (YARN-545) NodeResourceMonitor and its Impl are emty and may be removed

[ https://issues.apache.org/jira/browse/YARN-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-545: - Issue Type: Improvement (was: Bug) NodeResourceMonitor and its Impl are emty

[jira] [Updated] (YARN-100) container-executor should deal with stdout, stderr better

[ https://issues.apache.org/jira/browse/YARN-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-100: - Issue Type: Improvement (was: Bug) container-executor should deal with

[jira] [Resolved] (YARN-52) Seed TestYarnClient with tests

[ https://issues.apache.org/jira/browse/YARN-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-52. - Resolution: Duplicate Some tests are already added via some recent tickets. Closing

[jira] [Updated] (YARN-766) TestNodeManagerShutdown should use Shell to form the output path

[ https://issues.apache.org/jira/browse/YARN-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-766: - Issue Type: Improvement (was: Bug) TestNodeManagerShutdown should use Shell

[jira] [Commented] (YARN-245) Node Manager gives InvalidStateTransitonException for FINISH_APPLICATION at FINISHED

[ https://issues.apache.org/jira/browse/YARN-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702308#comment-13702308 ] Omkar Vinit Joshi commented on YARN-245: I think this will not fix the root cause.

[jira] [Commented] (YARN-149) ResourceManager (RM) High-Availability (HA)

[ https://issues.apache.org/jira/browse/YARN-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702365#comment-13702365 ] Alejandro Abdelnur commented on YARN-149: - Karthik, high level seems OK to me. One

[jira] [Commented] (YARN-149) ResourceManager (RM) High-Availability (HA)

[ https://issues.apache.org/jira/browse/YARN-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702378#comment-13702378 ] Bikas Saha commented on YARN-149: - Thanks for the notes Karthik. I will go through it and

[jira] [Commented] (YARN-894) NodeHealthScriptRunner timeout checking is inaccurate on Windows

[ https://issues.apache.org/jira/browse/YARN-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702402#comment-13702402 ] Chuan Liu commented on YARN-894: I only saw this once. After I did a clean and rebuild, I

[jira] [Updated] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-521: Attachment: YARN-521-1.patch Augment AM - RM client module to be able to request containers only at

[jira] [Commented] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

[ https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702424#comment-13702424 ] Sandy Ryza commented on YARN-521: - I uploaded a new patch that adds in the checks mentioned

[jira] [Updated] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-791: Attachment: YARN-791-8.patch Ensure that RM RPC APIs that return nodes are consistent with /nodes REST

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702427#comment-13702427 ] Sandy Ryza commented on YARN-791: - Uploaded a patch that updates the CLI documentation.

[jira] [Commented] (YARN-521) Augment AM - RM client module to be able to request containers only at specific locations

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

[jira] [Commented] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702443#comment-13702443 ] Jian He commented on YARN-513: -- bq.Does ResourceTrackerClientPBImpl still need a close method

[jira] [Commented] (YARN-513) Create common proxy client for communicating with RM

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702452#comment-13702452 ] Jian He commented on YARN-513: -- bq. Does this need an @VisibleForTesting flag? Yes, we need to

[jira] [Commented] (YARN-299) Node Manager throws org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: RESOURCE_FAILED at DONE

[ https://issues.apache.org/jira/browse/YARN-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702456#comment-13702456 ] Omkar Vinit Joshi commented on YARN-299: I guess the patch looks good overall ..

[jira] [Commented] (YARN-296) Resource Manager throws InvalidStateTransitonException: Invalid event: APP_ACCEPTED at RUNNING for RMAppImpl

[ https://issues.apache.org/jira/browse/YARN-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702464#comment-13702464 ] Zhijie Shen commented on YARN-296: -- The patch should work, but IMHO, the essential problem

[jira] [Updated] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

[ https://issues.apache.org/jira/browse/YARN-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-727: --- Attachment: YARN-727.18.patch ClientRMProtocol.getAllApplications should accept ApplicationType as a

[jira] [Commented] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

[ https://issues.apache.org/jira/browse/YARN-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702511#comment-13702511 ] Xuan Gong commented on YARN-727: Thanks for the comments. Created a new patch to address the

[jira] [Updated] (YARN-369) Handle ( or throw a proper error when receiving) status updates from application masters that have not registered

[ https://issues.apache.org/jira/browse/YARN-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-369: --- Attachment: YARN-369-trunk-4.patch Thanks [~bikassaha] for the review. Incorporated all the comments.

[jira] [Commented] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

[ https://issues.apache.org/jira/browse/YARN-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702514#comment-13702514 ] Xuan Gong commented on YARN-727: Related MR changes are in

[jira] [Updated] (YARN-295) Resource Manager throws InvalidStateTransitonException: Invalid event: CONTAINER_FINISHED at ALLOCATED for RMAppAttemptImpl

[ https://issues.apache.org/jira/browse/YARN-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-295: --- Attachment: YARN-295-trunk-3.patch Thanks [~zjshen] for review. Updated the patch. Thanks, Mayank

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

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

[jira] [Commented] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702532#comment-13702532 ] Omkar Vinit Joshi commented on YARN-814: * Instead of putting string messages of

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702537#comment-13702537 ] Vinod Kumar Vavilapalli commented on YARN-791: -- The latest patch looks good to

[jira] [Commented] (YARN-369) Handle ( or throw a proper error when receiving) status updates from application masters that have not registered

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

[jira] [Commented] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

[ https://issues.apache.org/jira/browse/YARN-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702543#comment-13702543 ] Hitesh Shah commented on YARN-727: -- - Use MRJobConfig.MR_APPLICATION_TYPE instead of

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

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

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702565#comment-13702565 ] Sandy Ryza commented on YARN-791: - Thanks Vinod! I initially tried something similar to

[jira] [Commented] (YARN-295) Resource Manager throws InvalidStateTransitonException: Invalid event: CONTAINER_FINISHED at ALLOCATED for RMAppAttemptImpl

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

[jira] [Created] (YARN-904) Enable multiple QOP for ResourceManager

Benoy Antony created YARN-904: - Summary: Enable multiple QOP for ResourceManager Key: YARN-904 URL: https://issues.apache.org/jira/browse/YARN-904 Project: Hadoop YARN Issue Type: Improvement

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702585#comment-13702585 ] Vinod Kumar Vavilapalli commented on YARN-791: -- Yeah, I too saw that.

[jira] [Commented] (YARN-791) Ensure that RM RPC APIs that return nodes are consistent with /nodes REST API

[ https://issues.apache.org/jira/browse/YARN-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702595#comment-13702595 ] Sandy Ryza commented on YARN-791: - Totally agree. Filed YARN-905 and we can figure out the

[jira] [Created] (YARN-905) Add state filters to nodes CLI

Sandy Ryza created YARN-905: --- Summary: Add state filters to nodes CLI Key: YARN-905 URL: https://issues.apache.org/jira/browse/YARN-905 Project: Hadoop YARN Issue Type: Improvement Affects

[jira] [Updated] (YARN-905) Add state filters to nodes CLI

[ https://issues.apache.org/jira/browse/YARN-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-905: Assignee: (was: Sandy Ryza) Add state filters to nodes CLI --

[jira] [Assigned] (YARN-905) Add state filters to nodes CLI

[ https://issues.apache.org/jira/browse/YARN-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan reassigned YARN-905: Assignee: Wei Yan Add state filters to nodes CLI -- Key:

[jira] [Updated] (YARN-894) NodeHealthScriptRunner timeout checking is inaccurate on Windows

[ https://issues.apache.org/jira/browse/YARN-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated YARN-894: --- Hadoop Flags: Reviewed +1 for the patch. I'll commit this. I also cannot repro the problem that I

[jira] [Commented] (YARN-894) NodeHealthScriptRunner timeout checking is inaccurate on Windows

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

[jira] [Commented] (YARN-814) Difficult to diagnose a failed container launch when error due to invalid environment variable

[ https://issues.apache.org/jira/browse/YARN-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702646#comment-13702646 ] Omkar Vinit Joshi commented on YARN-814: * yeah... what I am saying is user can

[jira] [Updated] (YARN-894) NodeHealthScriptRunner timeout checking is inaccurate on Windows

[ https://issues.apache.org/jira/browse/YARN-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated YARN-894: --- Component/s: nodemanager NodeHealthScriptRunner timeout checking is inaccurate on Windows

[jira] [Commented] (YARN-366) Add a tracing async dispatcher to simplify debugging

[ https://issues.apache.org/jira/browse/YARN-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702689#comment-13702689 ] Sandy Ryza commented on YARN-366: - Rebased onto trunk again Add a tracing

[jira] [Updated] (YARN-366) Add a tracing async dispatcher to simplify debugging

[ https://issues.apache.org/jira/browse/YARN-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-366: Attachment: YARN-366-6.patch Add a tracing async dispatcher to simplify debugging

[jira] [Commented] (YARN-763) AMRMClientAsync should stop heartbeating after receiving shutdown from RM

[ https://issues.apache.org/jira/browse/YARN-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702693#comment-13702693 ] Xuan Gong commented on YARN-763: bq.On a different note, serviceStop() should not call

[jira] [Updated] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

[ https://issues.apache.org/jira/browse/YARN-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-727: --- Attachment: YARN-727.19.patch ClientRMProtocol.getAllApplications should accept ApplicationType as a

[jira] [Commented] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

[ https://issues.apache.org/jira/browse/YARN-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702719#comment-13702719 ] Xuan Gong commented on YARN-727: Recreate the patch based on the latest trunk, and address

[jira] [Updated] (YARN-661) NM fails to cleanup local directories for users

[ https://issues.apache.org/jira/browse/YARN-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-661: --- Attachment: YARN-661-20130708.patch NM fails to cleanup local directories for users

[jira] [Updated] (YARN-347) YARN node CLI should also show CPU info as memory info in node status

[ https://issues.apache.org/jira/browse/YARN-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-347: Attachment: YARN-347-v2.patch YARN node CLI should also show CPU info as memory info in node status

[jira] [Commented] (YARN-347) YARN node CLI should also show CPU info as memory info in node status

[ https://issues.apache.org/jira/browse/YARN-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702723#comment-13702723 ] Junping Du commented on YARN-347: - Sure. Rebase this patch against trunk in v2 patch.

[jira] [Updated] (YARN-763) AMRMClientAsync should stop heartbeating after receiving shutdown from RM

[ https://issues.apache.org/jira/browse/YARN-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-763: --- Attachment: YARN-763.3.patch AMRMClientAsync should stop heartbeating after receiving shutdown from RM

[jira] [Commented] (YARN-366) Add a tracing async dispatcher to simplify debugging

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

[jira] [Commented] (YARN-763) AMRMClientAsync should stop heartbeating after receiving shutdown from RM

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

[jira] [Commented] (YARN-661) NM fails to cleanup local directories for users

of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12591342/YARN-661-20130708.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 1

[jira] [Commented] (YARN-347) YARN node CLI should also show CPU info as memory info in node status

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

[jira] [Updated] (YARN-763) AMRMClientAsync should stop heartbeating after receiving shutdown from RM

[ https://issues.apache.org/jira/browse/YARN-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-763: --- Attachment: YARN-763.4.patch AMRMClientAsync should stop heartbeating after receiving shutdown from RM

[jira] [Updated] (YARN-763) AMRMClientAsync should stop heartbeating after receiving shutdown from RM

[ https://issues.apache.org/jira/browse/YARN-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-763: --- Attachment: YARN-763.5.patch AMRMClientAsync should stop heartbeating after receiving shutdown from RM

[jira] [Commented] (YARN-763) AMRMClientAsync should stop heartbeating after receiving shutdown from RM

[ https://issues.apache.org/jira/browse/YARN-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702799#comment-13702799 ] Xuan Gong commented on YARN-763: fix the test case failure AMRMClientAsync

[jira] [Commented] (YARN-727) ClientRMProtocol.getAllApplications should accept ApplicationType as a parameter

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

[jira] [Commented] (YARN-763) AMRMClientAsync should stop heartbeating after receiving shutdown from RM

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

[jira] [Commented] (YARN-592) Container logs lost for the application when NM gets restarted

[ https://issues.apache.org/jira/browse/YARN-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702823#comment-13702823 ] Omkar Vinit Joshi commented on YARN-592: I just looked at your patch I need more

[jira] [Commented] (YARN-644) Basic null check is not performed on passed in arguments before using them in ContainerManagerImpl.startContainer

[ https://issues.apache.org/jira/browse/YARN-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702870#comment-13702870 ] Joseph Kniest commented on YARN-644: I'm new to mapreduce2/yarn dev and am unfamiliar

[jira] [Updated] (YARN-299) Node Manager throws org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: RESOURCE_FAILED at DONE

[ https://issues.apache.org/jira/browse/YARN-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-299: --- Attachment: YARN-299-trunk-2.patch Updating the patch. Thanks, Mayank Node Manager

[jira] [Commented] (YARN-299) Node Manager throws org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: RESOURCE_FAILED at DONE

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

[jira] [Commented] (YARN-875) Application can hang if AMRMClientAsync callback thread has exception

[ https://issues.apache.org/jira/browse/YARN-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702933#comment-13702933 ] Xuan Gong commented on YARN-875: For the callback, we can catch Throwable, and call

[jira] [Commented] (YARN-873) YARNClient.getApplicationReport(unknownAppId) returns a null report

[ https://issues.apache.org/jira/browse/YARN-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702938#comment-13702938 ] Xuan Gong commented on YARN-873: [~bikassaha] any comments

[jira] [Commented] (YARN-643) WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition

[ https://issues.apache.org/jira/browse/YARN-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702940#comment-13702940 ] Xuan Gong commented on YARN-643: [~vinodkv] any comments ? WHY appToken is

[jira] [Commented] (YARN-296) Resource Manager throws InvalidStateTransitonException: Invalid event: APP_ACCEPTED at RUNNING for RMAppImpl

[ https://issues.apache.org/jira/browse/YARN-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13702942#comment-13702942 ] Mayank Bansal commented on YARN-296: Thanks [~zjshen] and [~ojoshi] for the review I