[jira] [Commented] (YARN-169) Update log4j.appender.EventCounter to use org.apache.hadoop.log.metrics.EventCounter

[ https://issues.apache.org/jira/browse/YARN-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13674396#comment-13674396 ] Ravi Prakash commented on YARN-169: --- Hi! Could this please be merged into branch-0.23 as

[jira] [Resolved] (YARN-798) compiling program in hadoop 2

[ https://issues.apache.org/jira/browse/YARN-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash resolved YARN-798. --- Resolution: Not A Problem Please email the u...@hadoop.apache.org list. JIRA is for reporting problems

[jira] [Updated] (YARN-379) yarn [node,application] command print logger info messages

[ https://issues.apache.org/jira/browse/YARN-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-379: -- Attachment: YARN-379.patch This patch sets the log level to WARN for console. I tested by building

[jira] [Assigned] (YARN-379) yarn [node,application] command print logger info messages

[ https://issues.apache.org/jira/browse/YARN-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash reassigned YARN-379: - Assignee: Ravi Prakash (was: Abhishek Kapoor) yarn [node,application] command print logger

[jira] [Commented] (YARN-379) yarn [node,application] command print logger info messages

[ https://issues.apache.org/jira/browse/YARN-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682666#comment-13682666 ] Ravi Prakash commented on YARN-379: --- Hi Abhishek! Thanks for the contribution. I can help

[jira] [Commented] (YARN-339) TestResourceTrackerService is failing intermittently

[ https://issues.apache.org/jira/browse/YARN-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692270#comment-13692270 ] Ravi Prakash commented on YARN-339: --- Hi Vinod! Nopes! I can't reproduce this anymore.

[jira] [Resolved] (YARN-379) yarn [node,application] command print logger info messages

[ https://issues.apache.org/jira/browse/YARN-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash resolved YARN-379. --- Resolution: Not A Problem Fix Version/s: 2.2.0 This issue seems to have been fixed by YARN-530.

[jira] [Commented] (YARN-685) Capacity Scheduler is not distributing the reducers tasks across the cluster

[ https://issues.apache.org/jira/browse/YARN-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707290#comment-13707290 ] Ravi Prakash commented on YARN-685: --- This is not the behavior I am seeing in 0.23 / 2.2.

[jira] [Commented] (YARN-685) Capacity Scheduler is not distributing the reducers tasks across the cluster

[ https://issues.apache.org/jira/browse/YARN-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707292#comment-13707292 ] Ravi Prakash commented on YARN-685: --- I meant a randomwriter with 490 maps and 0 reduces.

[jira] [Commented] (YARN-685) Capacity Scheduler is not distributing the reducers tasks across the cluster

[ https://issues.apache.org/jira/browse/YARN-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13713976#comment-13713976 ] Ravi Prakash commented on YARN-685: --- The first column is the number of nodes. The second

[jira] [Created] (YARN-985) Nodemanager should log where a resource was localized

Ravi Prakash created YARN-985: - Summary: Nodemanager should log where a resource was localized Key: YARN-985 URL: https://issues.apache.org/jira/browse/YARN-985 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-985) Nodemanager should log where a resource was localized

[ https://issues.apache.org/jira/browse/YARN-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-985: -- Attachment: YARN-985.patch Patch applies cleanly to 0.23. With a little fuzz on trunk.

[jira] [Commented] (YARN-985) Nodemanager should log where a resource was localized

[ https://issues.apache.org/jira/browse/YARN-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13722730#comment-13722730 ] Ravi Prakash commented on YARN-985: --- Hi Omkar! Thanks for your quick review. We are facing

[jira] [Commented] (YARN-985) Nodemanager should log where a resource was localized

[ https://issues.apache.org/jira/browse/YARN-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725610#comment-13725610 ] Ravi Prakash commented on YARN-985: --- Hi Omkar! bq. yeah this is a small thing but would

[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=13730850#comment-13730850 ] Ravi Prakash commented on YARN-90: -- Do we know what we need to do for this JIRA? I can see

[jira] [Updated] (YARN-985) Nodemanager should log where a resource was localized

[ https://issues.apache.org/jira/browse/YARN-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-985: -- Attachment: YARN-985.branch-0.23.patch For branch-0.23 Nodemanager should log where a

[jira] [Updated] (YARN-985) Nodemanager should log where a resource was localized

[ https://issues.apache.org/jira/browse/YARN-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-985: -- Attachment: YARN-985.patch This is for trunk. I've incorporated Omkar's suggestion now

[jira] [Created] (YARN-1036) Distributed Cache gives inconsistent result if cache files get deleted from task tracker

Ravi Prakash created YARN-1036: -- Summary: Distributed Cache gives inconsistent result if cache files get deleted from task tracker Key: YARN-1036 URL: https://issues.apache.org/jira/browse/YARN-1036

[jira] [Updated] (YARN-1036) Distributed Cache gives inconsistent result if cache files get deleted from task tracker

[ https://issues.apache.org/jira/browse/YARN-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-1036: --- Attachment: YARN-1036.branch-0.23.patch This is exactly the same patch as MAPREDUCE-4342.

[jira] [Commented] (YARN-1036) Distributed Cache gives inconsistent result if cache files get deleted from task tracker

[ https://issues.apache.org/jira/browse/YARN-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13732125#comment-13732125 ] Ravi Prakash commented on YARN-1036: Thanks for the review Omkar and Koji! Are you

[jira] [Commented] (YARN-1036) Distributed Cache gives inconsistent result if cache files get deleted from task tracker

[ https://issues.apache.org/jira/browse/YARN-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13732637#comment-13732637 ] Ravi Prakash commented on YARN-1036: Omkar! We don't want to delete a file. We want it

[jira] [Commented] (YARN-1036) Distributed Cache gives inconsistent result if cache files get deleted from task tracker

[ https://issues.apache.org/jira/browse/YARN-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13732731#comment-13732731 ] Ravi Prakash commented on YARN-1036: [~ojoshi] bq. (here we don't want to check

[jira] [Commented] (YARN-1036) Distributed Cache gives inconsistent result if cache files get deleted from task tracker

[ https://issues.apache.org/jira/browse/YARN-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13732738#comment-13732738 ] Ravi Prakash commented on YARN-1036: In the way you suggest {quote} {code} case

[jira] [Updated] (YARN-1036) Distributed Cache gives inconsistent result if cache files get deleted from task tracker

[ https://issues.apache.org/jira/browse/YARN-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-1036: --- Attachment: YARN-1036.branch-0.23.patch Distributed Cache gives inconsistent result if cache

[jira] [Commented] (YARN-1036) Distributed Cache gives inconsistent result if cache files get deleted from task tracker

[ https://issues.apache.org/jira/browse/YARN-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13733639#comment-13733639 ] Ravi Prakash commented on YARN-1036: Hi Omkar! Thanks a lot for pointing out the

[jira] [Updated] (YARN-1036) Distributed Cache gives inconsistent result if cache files get deleted from task tracker

[ https://issues.apache.org/jira/browse/YARN-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-1036: --- Attachment: YARN-1036.branch-0.23.patch Thanks Jason and Omkar for your comments. Ok. Here is the

[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=13777082#comment-13777082 ] Ravi Prakash commented on YARN-90: -- Hi nijel! Welcome to the community and thanks for your

[jira] [Commented] (YARN-2348) ResourceManager web UI should display locale time instead of UTC time

[ https://issues.apache.org/jira/browse/YARN-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075781#comment-14075781 ] Ravi Prakash commented on YARN-2348: -1 on the patch as is. I could stomach an option

[jira] [Commented] (YARN-2424) LCE should support non-cgroups, non-secure mode

[ https://issues.apache.org/jira/browse/YARN-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14101509#comment-14101509 ] Ravi Prakash commented on YARN-2424: Thanks Tucu for pointing out the security

[jira] [Updated] (YARN-2424) LCE should support non-cgroups, non-secure mode

[ https://issues.apache.org/jira/browse/YARN-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-2424: --- Labels: (was: regression) LCE should support non-cgroups, non-secure mode

[jira] [Commented] (YARN-2424) LCE should support non-cgroups, non-secure mode

[ https://issues.apache.org/jira/browse/YARN-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14101677#comment-14101677 ] Ravi Prakash commented on YARN-2424: Hi Tucu! Thanks for your comment. There is

[jira] [Commented] (YARN-2424) LCE should support non-cgroups, non-secure mode

[ https://issues.apache.org/jira/browse/YARN-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14102554#comment-14102554 ] Ravi Prakash commented on YARN-2424: Hi Tucu! bq. If security is OFF, I can simply

[jira] [Commented] (YARN-2424) LCE should support non-cgroups, non-secure mode

[ https://issues.apache.org/jira/browse/YARN-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14102684#comment-14102684 ] Ravi Prakash commented on YARN-2424: Thanks Tucu! In YARN-1253, Vinod wrote: bq. Even

[jira] [Commented] (YARN-2424) LCE should support non-cgroups, non-secure mode

[ https://issues.apache.org/jira/browse/YARN-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14102873#comment-14102873 ] Ravi Prakash commented on YARN-2424: Hi Tucu! I'd brought it up only because in the

[jira] [Commented] (YARN-2424) LCE should support non-cgroups, non-secure mode

[ https://issues.apache.org/jira/browse/YARN-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14103046#comment-14103046 ] Ravi Prakash commented on YARN-2424: Hi Tucu! The intention was for this to be a useful

[jira] [Commented] (YARN-2424) LCE should support non-cgroups, non-secure mode

[ https://issues.apache.org/jira/browse/YARN-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14103151#comment-14103151 ] Ravi Prakash commented on YARN-2424: Hi Tucu! It is a perfectly valid production

[jira] [Commented] (YARN-2424) LCE should support non-cgroups, non-secure mode

[ https://issues.apache.org/jira/browse/YARN-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14104893#comment-14104893 ] Ravi Prakash commented on YARN-2424: I reviewed the code and the changes make sense to

[jira] [Commented] (YARN-2436) [post-HADOOP-9902] yarn application help doesn't work

[ https://issues.apache.org/jira/browse/YARN-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14105988#comment-14105988 ] Ravi Prakash commented on YARN-2436: Patch lgtm. +1. Tested $ yarn application help;

[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: -- Assignee: (was: Ravi Prakash) If AM fails due to overrunning resource limits, error not visible

[jira] [Created] (YARN-167) AM stuck in KILL_WAIT for days when node is lost in the middle

Ravi Prakash created YARN-167: - Summary: AM stuck in KILL_WAIT for days when node is lost in the middle Key: YARN-167 URL: https://issues.apache.org/jira/browse/YARN-167 Project: Hadoop YARN

[jira] [Commented] (YARN-167) AM stuck in KILL_WAIT for days

[ https://issues.apache.org/jira/browse/YARN-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13483339#comment-13483339 ] Ravi Prakash commented on YARN-167: --- bq. This is fine. Job waits for all tasks and

[jira] [Assigned] (YARN-151) Browser thinks RM main page JS is taking too long

[ https://issues.apache.org/jira/browse/YARN-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash reassigned YARN-151: - Assignee: Ravi Prakash Browser thinks RM main page JS is taking too long

[jira] [Commented] (YARN-151) Browser thinks RM main page JS is taking too long

[ https://issues.apache.org/jira/browse/YARN-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13487317#comment-13487317 ] Ravi Prakash commented on YARN-151: --- @Luke: Even if we used deferred rendering, it seems

[jira] [Updated] (YARN-151) Browser thinks RM main page JS is taking too long

[ https://issues.apache.org/jira/browse/YARN-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-151: -- Attachment: test.html Hi Luke! Thanks a lot for your prompt reply. :) 2 jobs on the JHS resulted in

[jira] [Updated] (YARN-151) Browser thinks RM main page JS is taking too long

[ https://issues.apache.org/jira/browse/YARN-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-151: -- Attachment: testDeferred.tar.gz Ok Luke! I'm convinced. Deferred rendering is AWESOME! :) Attaching the

[jira] [Updated] (YARN-151) Browser thinks RM main page JS is taking too long

[ https://issues.apache.org/jira/browse/YARN-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-151: -- Attachment: YARN-151.patch The same patch applies to all 3 branches : 0.23, branch-2, trunk

[jira] [Updated] (YARN-151) Browser thinks RM main page JS is taking too long

[ https://issues.apache.org/jira/browse/YARN-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-151: -- Affects Version/s: 2.0.2-alpha 0.23.4 Browser thinks RM main page JS is

[jira] [Created] (YARN-237) Refreshing the RM page forgets how many rows I had in my Datatables

Ravi Prakash created YARN-237: - Summary: Refreshing the RM page forgets how many rows I had in my Datatables Key: YARN-237 URL: https://issues.apache.org/jira/browse/YARN-237 Project: Hadoop YARN

[jira] [Created] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

Ravi Prakash created YARN-249: - Summary: Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x) Key: YARN-249 URL: https://issues.apache.org/jira/browse/YARN-249

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.patch This adds required functionality Capacity Scheduler web

[jira] [Created] (YARN-258) RM web page UI shows Invalid Date for start and finish times

Ravi Prakash created YARN-258: - Summary: RM web page UI shows Invalid Date for start and finish times Key: YARN-258 URL: https://issues.apache.org/jira/browse/YARN-258 Project: Hadoop YARN

[jira] [Updated] (YARN-258) RM web page UI shows Invalid Date for start and finish times

[ https://issues.apache.org/jira/browse/YARN-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-258: -- Attachment: YARN-258.patch This patch fixes the issue RM web page UI shows Invalid

[jira] [Updated] (YARN-258) RM web page UI shows Invalid Date for start and finish times

[ https://issues.apache.org/jira/browse/YARN-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-258: -- Description: Whenever the number of jobs was greater than a 100, two javascript arrays were being

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.patch Hi Jeagles! Thanks for your review. I have fixed the divide by 0 and moved

[jira] [Updated] (YARN-266) RM and JHS Web UIs are blank because AppsBlock is not escaping string properly

[ https://issues.apache.org/jira/browse/YARN-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-266: -- Attachment: YARN-266.patch Simple patch to fix the issue. RM and JHS Web UIs are

[jira] [Commented] (YARN-266) RM and JHS Web UIs are blank because AppsBlock is not escaping string properly

[ https://issues.apache.org/jira/browse/YARN-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528696#comment-13528696 ] Ravi Prakash commented on YARN-266: --- I tested by submitting a bad job name (with a new

[jira] [Updated] (YARN-267) Fix fair scheduler web UI

[ https://issues.apache.org/jira/browse/YARN-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-267: -- Description: The fair scheduler web UI was broken by MAPREDUCE-4720. The queues area is not shown, and

[jira] [Commented] (YARN-267) Fix fair scheduler web UI

[ https://issues.apache.org/jira/browse/YARN-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13529757#comment-13529757 ] Ravi Prakash commented on YARN-267: --- Sorry about this Sandy! I dug and guess that it was

[jira] [Created] (YARN-268) Capacity Scheduler Web UI is throwing a JavaScript Exception

Ravi Prakash created YARN-268: - Summary: Capacity Scheduler Web UI is throwing a JavaScript Exception Key: YARN-268 URL: https://issues.apache.org/jira/browse/YARN-268 Project: Hadoop YARN

[jira] [Resolved] (YARN-268) Capacity Scheduler Web UI is throwing a JavaScript Exception

[ https://issues.apache.org/jira/browse/YARN-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash resolved YARN-268. --- Resolution: Invalid This is funny! This only happens when I have my Firebug debugger on. I'm going to

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.branch-0.23.patch Patch for branch-0.23 Capacity Scheduler web

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.patch Patch for trunk. Capacity Scheduler web page should show

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.branch-0.23.patch Test was failing because MockRM.submitApp had been submitting

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.patch In trunk, vCores has been added to Resources. Hence the test I added was

[jira] [Created] (YARN-339) TestResourceTrackerService is failing intermittently

Ravi Prakash created YARN-339: - Summary: TestResourceTrackerService is failing intermittently Key: YARN-339 URL: https://issues.apache.org/jira/browse/YARN-339 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.png Release audit warnings are not related to this patch. The output on the

[jira] [Commented] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552878#comment-13552878 ] Ravi Prakash commented on YARN-249: ---

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.branch-0.23.patch Capacity Scheduler web page should show list of active users

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.patch Capacity Scheduler web page should show list of active users per queue

[jira] [Updated] (YARN-133) update web services docs for RM clusterMetrics

[ https://issues.apache.org/jira/browse/YARN-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-133: -- Attachment: YARN-133.patch Simple patch update web services docs for RM clusterMetrics

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.branch-0.23.patch Updated patch for branch-0.23 Capacity

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.patch Updated patch for trunk Capacity Scheduler web page should

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.branch-0.23.patch Updated docs to include active and pending applications

[jira] [Commented] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13572709#comment-13572709 ] Ravi Prakash commented on YARN-249: --- Thanks a lot for your review Tom! I've incorporated

[jira] [Updated] (YARN-362) Unexpected extra results when using the task attempt table search

[ https://issues.apache.org/jira/browse/YARN-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-362: -- Attachment: YARN-362.branch-0.23.patch Thanks for the review Jason! I hadn't realized that I hadn't

[jira] [Updated] (YARN-362) Unexpected extra results when using the task attempt table search

[ https://issues.apache.org/jira/browse/YARN-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-362: -- Attachment: YARN-362.patch The patch ported to trunk Unexpected extra results when

[jira] [Commented] (YARN-362) Unexpected extra results when using the task attempt table search

[ https://issues.apache.org/jira/browse/YARN-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573686#comment-13573686 ] Ravi Prakash commented on YARN-362: --- I manually tested the patch. Looks good to me. +1 :D

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.branch-0.23.patch Thanks for all the comments Tom! I've incorporated all your

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.patch And this one is for trunk Capacity Scheduler web page

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.branch-0.23.patch Changed UserInfo to not know about LeafQueue.User

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.patch Same for trunk Capacity Scheduler web page should show list

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.branch-0.23.patch Appeasing findbugs warning. Capacity Scheduler

[jira] [Updated] (YARN-249) Capacity Scheduler web page should show list of active users per queue like it used to (in 1.x)

[ https://issues.apache.org/jira/browse/YARN-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-249: -- Attachment: YARN-249.patch Same for trunk Capacity Scheduler web page should show

[jira] [Assigned] (YARN-200) yarn log does not output all needed information, and is in a binary format

[ https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash reassigned YARN-200: - Assignee: Ravi Prakash yarn log does not output all needed information, and is in a binary

[jira] [Updated] (YARN-200) yarn log does not output all needed information, and is in a binary format

[ https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-200: -- Attachment: YARN-200.patch This patch applies to trunk as well as 0.23. Can someone please review and

[jira] [Commented] (YARN-200) yarn log does not output all needed information, and is in a binary format

[ https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13605166#comment-13605166 ] Ravi Prakash commented on YARN-200: --- All these requests come courtesy Koji!

[jira] [Updated] (YARN-200) yarn log does not output all needed information, and is in a binary format

[ https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-200: -- Attachment: YARN-200.patch Sorry about the earlier patch. Somehow, not compiling the entire source tree

[jira] [Commented] (YARN-200) yarn log does not output all needed information, and is in a binary format

[ https://issues.apache.org/jira/browse/YARN-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606564#comment-13606564 ] Ravi Prakash commented on YARN-200: --- Jason suggested I should check if unicode characters

[jira] [Commented] (YARN-379) yarn [node,application] command print logger info messages

[ https://issues.apache.org/jira/browse/YARN-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13608213#comment-13608213 ] Ravi Prakash commented on YARN-379: --- Can we not simply add

[jira] [Resolved] (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 ] Ravi Prakash resolved YARN-501. --- Resolution: Not A Problem Hi Krishna, Please set yarn.app.mapreduce.am.command-opts to include a more

[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] [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] [Updated] (YARN-586) Typo in ApplicationSubmissionContext#setApplicationId

[ https://issues.apache.org/jira/browse/YARN-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-586: -- Assignee: Zhijie Shen (was: Ravi Prakash) Typo in ApplicationSubmissionContext#setApplicationId

[jira] [Assigned] (YARN-586) Typo in ApplicationSubmissionContext#setApplicationId

[ https://issues.apache.org/jira/browse/YARN-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash reassigned YARN-586: - Assignee: Ravi Prakash (was: Zhijie Shen) Typo in

[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: RMAppAttemptImplsmall.png State diagram for reference If AM fails due to

[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=13651078#comment-13651078 ] Ravi Prakash commented on YARN-560: --- {quote} * In the usual case of NM killing AM while it

[jira] [Commented] (YARN-379) yarn [node,application] command print logger info messages

[ https://issues.apache.org/jira/browse/YARN-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13657320#comment-13657320 ] Ravi Prakash commented on YARN-379: --- Hi Abhishek, I recant. I like the patch's approach

[jira] [Commented] (YARN-379) yarn [node,application] command print logger info messages

[ https://issues.apache.org/jira/browse/YARN-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658403#comment-13658403 ] Ravi Prakash commented on YARN-379: --- I recant my recant. So many options. We probably

[jira] [Commented] (YARN-1768) yarn kill non-existent application is too verbose

[ https://issues.apache.org/jira/browse/YARN-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13918381#comment-13918381 ] Ravi Prakash commented on YARN-1768: With this patch the return code is wrong (0).

[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=13918439#comment-13918439 ] Ravi Prakash commented on YARN-90: -- I'm not working on it. Please feel free to take it over.

  1   2   3   >