[jira] [Updated] (YARN-186) Coverage fixing LinuxContainerExecuror

[ https://issues.apache.org/jira/browse/YARN-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Gorshkov updated YARN-186: -- Attachment: (was: YARN-186-branch-2.patch) Coverage fixing LinuxContainerExecuror

[jira] [Updated] (YARN-186) Coverage fixing LinuxContainerExecuror

[ https://issues.apache.org/jira/browse/YARN-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Gorshkov updated YARN-186: -- Attachment: (was: YARN-186-trunk.patch) Coverage fixing LinuxContainerExecuror

[jira] [Updated] (YARN-186) Coverage fixing LinuxContainerExecuror

[ https://issues.apache.org/jira/browse/YARN-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Gorshkov updated YARN-186: -- Attachment: YARN-186-branch-2.patch YARN-186-branch-0.23.patch Coverage

[jira] [Updated] (YARN-186) Coverage fixing LinuxContainerExecuror

[ https://issues.apache.org/jira/browse/YARN-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Gorshkov updated YARN-186: -- Attachment: YARN-186-trunk.patch Coverage fixing LinuxContainerExecuror

[jira] [Commented] (YARN-189) deadlock in RM - AMResponse object

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

[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] [Commented] (YARN-165) RM should point tracking URL to RM web page for app when AM fails

[ https://issues.apache.org/jira/browse/YARN-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13487843#comment-13487843 ] Jason Lowe commented on YARN-165: - Sorry I should have mentioned that I performed some

[jira] [Updated] (YARN-165) RM should point tracking URL to RM web page for app when AM fails

[ https://issues.apache.org/jira/browse/YARN-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-165: Attachment: YARN-165-branch23.patch Patch for branch-0.23. RM should point tracking URL to

[jira] [Updated] (YARN-166) capacity scheduler doesn't allow capacity 1.0

[ https://issues.apache.org/jira/browse/YARN-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-166: --- Attachment: YARN-166.patch Fixes so that capacity can be 1. It allows you to actually set capacity

[jira] [Commented] (YARN-165) RM should point tracking URL to RM web page for app when AM fails

[ https://issues.apache.org/jira/browse/YARN-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13487892#comment-13487892 ] Robert Parker commented on YARN-165: I am getting an NPE on the test added by

[jira] [Commented] (YARN-165) RM should point tracking URL to RM web page for app when AM fails

[ https://issues.apache.org/jira/browse/YARN-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13487895#comment-13487895 ] Robert Joseph Evans commented on YARN-165: -- Holding off on checking in 0.23. The

[jira] [Updated] (YARN-165) RM should point tracking URL to RM web page for app when AM fails

[ https://issues.apache.org/jira/browse/YARN-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-165: Attachment: YARN-165-branch23.patch Sorry, my bad. I manually tested the fix just like I did for the trunk

[jira] [Commented] (YARN-166) capacity scheduler doesn't allow capacity 1.0

[ https://issues.apache.org/jira/browse/YARN-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13487900#comment-13487900 ] Robert Joseph Evans commented on YARN-166: -- The changes look good to me. My only

[jira] [Commented] (YARN-166) capacity scheduler doesn't allow capacity 1.0

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

[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] [Commented] (YARN-189) deadlock in RM - AMResponse object

[ https://issues.apache.org/jira/browse/YARN-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13488125#comment-13488125 ] Robert Joseph Evans commented on YARN-189: -- The new patch looks good too. I am +1

[jira] [Commented] (YARN-165) RM should point tracking URL to RM web page for app when AM fails

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

[jira] [Commented] (YARN-166) capacity scheduler doesn't allow capacity 1.0

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

[jira] [Commented] (YARN-159) RM web ui applications page should be sorted to display last app first

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

[jira] [Commented] (YARN-189) deadlock in RM - AMResponse object

[ https://issues.apache.org/jira/browse/YARN-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13488385#comment-13488385 ] Vinod Kumar Vavilapalli commented on YARN-189: -- File MAPREDUCE-4761 for the MR

[jira] [Moved] (YARN-195) AM should have a way of telling RM to not allocate containers on some nodes

[ https://issues.apache.org/jira/browse/YARN-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli moved MAPREDUCE-3314 to YARN-195: - Tags: (was: mr2,mapreduce-2.0)

[jira] [Moved] (YARN-196) Nodemanager if started before starting Resource manager is getting shutdown.But if both RM and NM are started and then after if RM is going down,NM is retrying for the RM.

[ https://issues.apache.org/jira/browse/YARN-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli moved MAPREDUCE-3676 to YARN-196: - Component/s: (was: mrv2)

[jira] [Moved] (YARN-197) Add a separate log server

[ https://issues.apache.org/jira/browse/YARN-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli moved MAPREDUCE-3300 to YARN-197: - Component/s: (was: mrv2) Affects

[jira] [Moved] (YARN-198) If we are navigating to Nodemanager UI from Resourcemanager,then there is not link to navigate back to Resource manager

[ https://issues.apache.org/jira/browse/YARN-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli moved MAPREDUCE-4125 to YARN-198: - Component/s: (was: mrv2)