[jira] [Commented] (YARN-1358) TestYarnCLI fails on Windows due to line endings

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

[jira] [Commented] (YARN-1357) TestContainerLaunch.testContainerEnvVariables fails on Windows

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

[jira] [Commented] (YARN-1343) NodeManagers additions/restarts are not reported as node updates in AllocateResponse responses to AMs

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

[jira] [Commented] (YARN-1321) NMTokenCache is a singleton, prevents multiple AMs running in a single JVM to work correctly

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

[jira] [Commented] (YARN-1031) JQuery UI components reference external css in branch-23

[ https://issues.apache.org/jira/browse/YARN-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810156#comment-13810156 ] Hudson commented on YARN-1031: -- FAILURE: Integrated in Hadoop-Hdfs-0.23-Build #777 (See

[jira] [Commented] (YARN-1321) NMTokenCache is a singleton, prevents multiple AMs running in a single JVM to work correctly

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

[jira] [Commented] (YARN-1357) TestContainerLaunch.testContainerEnvVariables fails on Windows

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

[jira] [Commented] (YARN-1358) TestYarnCLI fails on Windows due to line endings

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

[jira] [Commented] (YARN-1343) NodeManagers additions/restarts are not reported as node updates in AllocateResponse responses to AMs

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

[jira] [Commented] (YARN-1321) NMTokenCache is a singleton, prevents multiple AMs running in a single JVM to work correctly

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

[jira] [Commented] (YARN-1357) TestContainerLaunch.testContainerEnvVariables fails on Windows

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

[jira] [Commented] (YARN-1343) NodeManagers additions/restarts are not reported as node updates in AllocateResponse responses to AMs

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

[jira] [Commented] (YARN-1358) TestYarnCLI fails on Windows due to line endings

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

[jira] [Commented] (YARN-1324) NodeManager potentially causes unnecessary operations on all its disks

[ https://issues.apache.org/jira/browse/YARN-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810228#comment-13810228 ] Jason Lowe commented on YARN-1324: -- +1 for randomizing the list of directories. Even if

[jira] [Commented] (YARN-1374) Resource Manager fails to start due to ConcurrentModificationException

[ https://issues.apache.org/jira/browse/YARN-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810364#comment-13810364 ] Steve Loughran commented on YARN-1374: -- while this patch fixes a symptom, it doesn't

[jira] [Updated] (YARN-1381) Same relaxLocality appears twice in exception message of AMRMClientImpl#checkLocalityRelaxationConflict()

[ https://issues.apache.org/jira/browse/YARN-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated YARN-1381: - Attachment: yarn-1381.patch Same relaxLocality appears twice in exception message of

[jira] [Commented] (YARN-1374) Resource Manager fails to start due to ConcurrentModificationException

[ https://issues.apache.org/jira/browse/YARN-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810448#comment-13810448 ] Bikas Saha commented on YARN-1374: -- Wouldnt it be incorrect to add a new service to an

[jira] [Commented] (YARN-1381) Same relaxLocality appears twice in exception message of AMRMClientImpl#checkLocalityRelaxationConflict()

[ https://issues.apache.org/jira/browse/YARN-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810457#comment-13810457 ] Ted Yu commented on YARN-1381: -- I use the same Eclipse formatter for HBase where line can be

[jira] [Commented] (YARN-891) Store completed application information in RM state store

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

[jira] [Created] (YARN-1382) NodeListManager has a memory leak, unusableRMNodesConcurrentSet is never purged

Alejandro Abdelnur created YARN-1382: Summary: NodeListManager has a memory leak, unusableRMNodesConcurrentSet is never purged Key: YARN-1382 URL: https://issues.apache.org/jira/browse/YARN-1382

[jira] [Commented] (YARN-987) Adding History Service to use Store and converting Historydata to Report

[ https://issues.apache.org/jira/browse/YARN-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810557#comment-13810557 ] Mayank Bansal commented on YARN-987: Thanks [~zjshen] for the review. bq. Do we really

[jira] [Updated] (YARN-987) Adding History Service to use Store and converting Historydata to Report

[ https://issues.apache.org/jira/browse/YARN-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-987: --- Attachment: YARN-987-4.patch Attaching latest patch. Thanks, Mayank Adding History Service to use

[jira] [Commented] (YARN-546) mapred.fairscheduler.eventlog.enabled removed from Hadoop 2.0

[ https://issues.apache.org/jira/browse/YARN-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810565#comment-13810565 ] Joep Rottinghuis commented on YARN-546: --- [~sandyr] didn't you mention that you fixed

[jira] [Commented] (YARN-987) Adding History Service to use Store and converting Historydata to Report

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

[jira] [Commented] (YARN-1380) Enable NM to automatically reuse failed local dirs after they are available again

[ https://issues.apache.org/jira/browse/YARN-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810586#comment-13810586 ] Vinod Kumar Vavilapalli commented on YARN-1380: --- Duplicate of YARN-90.

[jira] [Resolved] (YARN-1380) Enable NM to automatically reuse failed local dirs after they are available again

[ https://issues.apache.org/jira/browse/YARN-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-1380. --- Resolution: Duplicate Enable NM to automatically reuse failed local dirs

[jira] [Commented] (YARN-1374) Resource Manager fails to start due to ConcurrentModificationException

[ https://issues.apache.org/jira/browse/YARN-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810613#comment-13810613 ] Karthik Kambatla commented on YARN-1374: Also, the patch fixes another bug. Without

[jira] [Updated] (YARN-786) Expose application resource usage in RM REST API

[ https://issues.apache.org/jira/browse/YARN-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-786: Attachment: YARN-786-1.patch Expose application resource usage in RM REST API

[jira] [Commented] (YARN-786) Expose application resource usage in RM REST API

[ https://issues.apache.org/jira/browse/YARN-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810652#comment-13810652 ] Sandy Ryza commented on YARN-786: - Uploaded a new patch with updated documentation. Expose

[jira] [Commented] (YARN-786) Expose application resource usage in RM REST API

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

[jira] [Updated] (YARN-1320) Custom log4j properties in Distributed shell does not work properly.

[ https://issues.apache.org/jira/browse/YARN-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1320: Attachment: YARN-1320.4.patch Add a test case. We set custom log4j property to output debug level message.

[jira] [Updated] (YARN-786) Expose application resource usage in RM REST API

[ https://issues.apache.org/jira/browse/YARN-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-786: Attachment: YARN-786-2.patch Expose application resource usage in RM REST API

[jira] [Commented] (YARN-1320) Custom log4j properties in Distributed shell does not work properly.

[ https://issues.apache.org/jira/browse/YARN-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810667#comment-13810667 ] Xuan Gong commented on YARN-1320: - Did the manually test on a single node cluster.

[jira] [Commented] (YARN-1320) Custom log4j properties in Distributed shell does not work properly.

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

[jira] [Updated] (YARN-1320) Custom log4j properties in Distributed shell does not work properly.

[ https://issues.apache.org/jira/browse/YARN-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1320: Attachment: YARN-1320.4.patch Custom log4j properties in Distributed shell does not work properly.

[jira] [Commented] (YARN-786) Expose application resource usage in RM REST API

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

[jira] [Commented] (YARN-1381) Same relaxLocality appears twice in exception message of AMRMClientImpl#checkLocalityRelaxationConflict()

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

[jira] [Commented] (YARN-1320) Custom log4j properties in Distributed shell does not work properly.

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

[jira] [Commented] (YARN-786) Expose application resource usage in RM REST API

[ https://issues.apache.org/jira/browse/YARN-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810800#comment-13810800 ] Alejandro Abdelnur commented on YARN-786: - +1 Expose application resource usage in

[jira] [Commented] (YARN-1290) Let continuous scheduling achieve more balanced task assignment

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

[jira] [Updated] (YARN-1279) Expose a client API to allow clients to figure if log aggregation is complete

[ https://issues.apache.org/jira/browse/YARN-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1279: Attachment: YARN-1279.1.patch The patch includes all the changes in RM side and Client side. All the pb

[jira] [Created] (YARN-1383) Remove node updates from the Fair Scheduler event log

Sandy Ryza created YARN-1383: Summary: Remove node updates from the Fair Scheduler event log Key: YARN-1383 URL: https://issues.apache.org/jira/browse/YARN-1383 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-1383) Remove node updates from the Fair Scheduler event log

[ https://issues.apache.org/jira/browse/YARN-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1383: - Attachment: YARN-1383.patch Remove node updates from the Fair Scheduler event log

[jira] [Commented] (YARN-546) mapred.fairscheduler.eventlog.enabled removed from Hadoop 2.0

[ https://issues.apache.org/jira/browse/YARN-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810828#comment-13810828 ] Sandy Ryza commented on YARN-546: - I think the issue still exists. Just filed YARN-1383 to

[jira] [Commented] (YARN-1279) Expose a client API to allow clients to figure if log aggregation is complete

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

[jira] [Updated] (YARN-979) [YARN-321] Add more APIs related to ApplicationAttempt and Container in ApplicationHistoryProtocol

[ https://issues.apache.org/jira/browse/YARN-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-979: --- Attachment: YARN-979-4.patch Attaching the patch for latest YARN-321 branch. Thanks, Mayank

[jira] [Commented] (YARN-979) [YARN-321] Add more APIs related to ApplicationAttempt and Container in ApplicationHistoryProtocol

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

[jira] [Updated] (YARN-1378) Implement a RMStateStore cleaner for deleting application/attempt info

[ https://issues.apache.org/jira/browse/YARN-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1378: -- Attachment: YARN-1378.1.patch Upload a patch: - create a separate removeAppdispatcher in RMStateStore for

[jira] [Updated] (YARN-1279) Expose a client API to allow clients to figure if log aggregation is complete

[ https://issues.apache.org/jira/browse/YARN-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1279: Attachment: YARN-1279.2.patch update the patch based on the latest trunk Expose a client API to allow

[jira] [Commented] (YARN-1279) Expose a client API to allow clients to figure if log aggregation is complete

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

[jira] [Commented] (YARN-1378) Implement a RMStateStore cleaner for deleting application/attempt info

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

[jira] [Updated] (YARN-674) Slow or failing DelegationToken renewals on submission itself make RM unavailable

[ https://issues.apache.org/jira/browse/YARN-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-674: --- Attachment: YARN-674.4.patch Slow or failing DelegationToken renewals on submission itself

[jira] [Commented] (YARN-1210) During RM restart, RM should start a new attempt only when previous attempt exits for real

[ https://issues.apache.org/jira/browse/YARN-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810927#comment-13810927 ] Omkar Vinit Joshi commented on YARN-1210: - submitting patch on top of YARN-674.

[jira] [Updated] (YARN-1206) Container logs link is broken on RM web UI after application finished

[ https://issues.apache.org/jira/browse/YARN-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1206: -- Target Version/s: 2.3.0 Container logs link is broken on RM web UI after

[jira] [Commented] (YARN-674) Slow or failing DelegationToken renewals on submission itself make RM unavailable

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

[jira] [Commented] (YARN-90) NodeManager should identify failed disks becoming good back again

[ https://issues.apache.org/jira/browse/YARN-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810976#comment-13810976 ] Hou Song commented on YARN-90: -- Sorry for the last comment, I meant: For unit tests, I add a

[jira] [Updated] (YARN-1279) Expose a client API to allow clients to figure if log aggregation is complete

[ https://issues.apache.org/jira/browse/YARN-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1279: Attachment: YARN-1279.2.patch Expose a client API to allow clients to figure if log aggregation is

[jira] [Updated] (YARN-1320) Custom log4j properties in Distributed shell does not work properly.

[ https://issues.apache.org/jira/browse/YARN-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1320: Attachment: YARN-1320.4.patch Custom log4j properties in Distributed shell does not work properly.

[jira] [Updated] (YARN-1320) Custom log4j properties in Distributed shell does not work properly.

[ https://issues.apache.org/jira/browse/YARN-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1320: Attachment: YARN-1320.4.patch Custom log4j properties in Distributed shell does not work properly.

[jira] [Commented] (YARN-1320) Custom log4j properties in Distributed shell does not work properly.

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

[jira] [Updated] (YARN-1320) Custom log4j properties in Distributed shell does not work properly.

[ https://issues.apache.org/jira/browse/YARN-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1320: Attachment: YARN-1320.4.patch Custom log4j properties in Distributed shell does not work properly.

[jira] [Commented] (YARN-1320) Custom log4j properties in Distributed shell does not work properly.

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