[jira] [Commented] (YARN-188) Coverage fixing for CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498717#comment-13498717 ] Hudson commented on YARN-188: - Integrated in Hadoop-Yarn-trunk #38 (See [https://builds.apache.

[jira] [Commented] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498726#comment-13498726 ] Bikas Saha commented on YARN-128: - 1) Unless I am mistaken, the test condition is correct. a

[jira] [Commented] (YARN-188) Coverage fixing for CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498772#comment-13498772 ] Hudson commented on YARN-188: - Integrated in Hadoop-Hdfs-0.23-Build #437 (See [https://builds.a

[jira] [Commented] (YARN-188) Coverage fixing for CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498790#comment-13498790 ] Hudson commented on YARN-188: - Integrated in Hadoop-Hdfs-trunk #1228 (See [https://builds.apach

[jira] [Commented] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498800#comment-13498800 ] Arinto Murdopo commented on YARN-128: - 1) Yes, I agree with your clarification. It works

[jira] [Commented] (YARN-188) Coverage fixing for CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498806#comment-13498806 ] Hudson commented on YARN-188: - Integrated in Hadoop-Mapreduce-trunk #1259 (See [https://builds.

[jira] [Commented] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498825#comment-13498825 ] Tom White commented on YARN-128: Bikas, this looks good so far. Thanks for working on it. A

[jira] [Commented] (YARN-214) RMContainerImpl does not handle event EXPIRE at state RUNNING

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

[jira] [Updated] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-128: Attachment: restart-12-11-zkstore.patch > Resurrect RM Restart > - > >

[jira] [Commented] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498876#comment-13498876 ] Bikas Saha commented on YARN-128: - @Arinto Thanks for using the code! 1) Yes. Both are the s

[jira] [Created] (YARN-218) Distiguish between "failed" and "killed" app attempts

Tom White created YARN-218: -- Summary: Distiguish between "failed" and "killed" app attempts Key: YARN-218 URL: https://issues.apache.org/jira/browse/YARN-218 Project: Hadoop YARN Issue Type: New Fea

[jira] [Commented] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498883#comment-13498883 ] Tom White commented on YARN-128: You are right about there being no race - I missed the comm

[jira] [Commented] (YARN-214) RMContainerImpl does not handle event EXPIRE at state RUNNING

[ https://issues.apache.org/jira/browse/YARN-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498941#comment-13498941 ] Robert Joseph Evans commented on YARN-214: -- Now that I understand the code better I

[jira] [Updated] (YARN-214) RMContainerImpl does not handle event EXPIRE at state RUNNING

[ https://issues.apache.org/jira/browse/YARN-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated YARN-214: - Attachment: YARN-214.patch > RMContainerImpl does not handle event EXPIRE at state RUNNING > --

[jira] [Commented] (YARN-214) RMContainerImpl does not handle event EXPIRE at state RUNNING

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

[jira] [Commented] (YARN-214) RMContainerImpl does not handle event EXPIRE at state RUNNING

[ https://issues.apache.org/jira/browse/YARN-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498993#comment-13498993 ] Robert Joseph Evans commented on YARN-214: -- +1 the changes look good. I'll check t

[jira] [Created] (YARN-219) NM should aggregate logs when application finishes.

Robert Joseph Evans created YARN-219: Summary: NM should aggregate logs when application finishes. Key: YARN-219 URL: https://issues.apache.org/jira/browse/YARN-219 Project: Hadoop YARN I

[jira] [Commented] (YARN-214) RMContainerImpl does not handle event EXPIRE at state RUNNING

[ https://issues.apache.org/jira/browse/YARN-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499001#comment-13499001 ] Hudson commented on YARN-214: - Integrated in Hadoop-trunk-Commit #3032 (See [https://builds.apa

[jira] [Created] (YARN-220) NM should limit number of applications who's logs are being aggregated

Robert Joseph Evans created YARN-220: Summary: NM should limit number of applications who's logs are being aggregated Key: YARN-220 URL: https://issues.apache.org/jira/browse/YARN-220 Project: Had

[jira] [Created] (YARN-221) NM should provide a way for AM to tell it not to aggregate logs.

Robert Joseph Evans created YARN-221: Summary: NM should provide a way for AM to tell it not to aggregate logs. Key: YARN-221 URL: https://issues.apache.org/jira/browse/YARN-221 Project: Hadoop YA

[jira] [Commented] (YARN-85) Allow per job log aggregation configuration

[ https://issues.apache.org/jira/browse/YARN-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499012#comment-13499012 ] Robert Joseph Evans commented on YARN-85: - Once YARN-221 goes in we should be able to

[jira] [Assigned] (YARN-219) NM should aggregate logs when application finishes.

[ https://issues.apache.org/jira/browse/YARN-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans reassigned YARN-219: Assignee: Robert Joseph Evans > NM should aggregate logs when application finishe

[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-tabpanel&focusedCommentId=13499030#comment-13499030 ] Hadoop QA commented on YARN-151: {color:red}-1 overall{color}. Here are the results of test

[jira] [Commented] (YARN-221) NM should provide a way for AM to tell it not to aggregate logs.

[ https://issues.apache.org/jira/browse/YARN-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499106#comment-13499106 ] Siddharth Seth commented on YARN-221: - This is related to container re-use as well. Depe

[jira] [Commented] (YARN-162) nodemanager log aggregation has scaling issues with namenode

[ https://issues.apache.org/jira/browse/YARN-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499108#comment-13499108 ] Siddharth Seth commented on YARN-162: - Bobby, if you haven't gotten started working on t

[jira] [Updated] (YARN-219) NM should aggregate logs when application finishes.

[ https://issues.apache.org/jira/browse/YARN-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans updated YARN-219: - Priority: Critical (was: Major) Bumping the priority to critical because we are seeing a v

[jira] [Updated] (YARN-219) NM should aggregate logs when application finishes.

[ https://issues.apache.org/jira/browse/YARN-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans updated YARN-219: - Attachment: YARN-219.txt This patch is a bit ugly, but it does fix the issue. I wanted to

[jira] [Commented] (YARN-219) NM should aggregate logs when application finishes.

[ https://issues.apache.org/jira/browse/YARN-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499125#comment-13499125 ] Robert Joseph Evans commented on YARN-219: -- Sid from your comment on YARN-162. If y

[jira] [Commented] (YARN-219) NM should aggregate logs when application finishes.

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

[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-tabpanel&focusedCommentId=13499135#comment-13499135 ] Robert Joseph Evans commented on YARN-151: -- The patch looks good to me +1. I'll ch

[jira] [Updated] (YARN-162) nodemanager log aggregation has scaling issues with namenode

[ https://issues.apache.org/jira/browse/YARN-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-162: Attachment: YARN-162_WIP.txt Work in progress patch for YARN-219, YARN-220. Is a reasonably simple c

[jira] [Commented] (YARN-219) NM should aggregate logs when application finishes.

[ https://issues.apache.org/jira/browse/YARN-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499137#comment-13499137 ] Siddharth Seth commented on YARN-219: - Bobby, I've posted a patch to YARN-162 which I ca

[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-tabpanel&focusedCommentId=13499143#comment-13499143 ] Hudson commented on YARN-151: - Integrated in Hadoop-trunk-Commit #3033 (See [https://builds.apa

[jira] [Commented] (YARN-162) nodemanager log aggregation has scaling issues with namenode

[ https://issues.apache.org/jira/browse/YARN-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499191#comment-13499191 ] Robert Joseph Evans commented on YARN-162: -- The patch looks good as an initial star

[jira] [Updated] (YARN-162) nodemanager log aggregation has scaling issues with namenode

[ https://issues.apache.org/jira/browse/YARN-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-162: Attachment: YARN-162.txt Updated patch. Fixes the additional filesystem close, and a bunch of other

[jira] [Commented] (YARN-162) nodemanager log aggregation has scaling issues with namenode

[ https://issues.apache.org/jira/browse/YARN-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499232#comment-13499232 ] Siddharth Seth commented on YARN-162: - The patch does change behaviour. Prior to this, d

[jira] [Created] (YARN-222) Fair scheduler should create queue for each user by default

Sandy Ryza created YARN-222: --- Summary: Fair scheduler should create queue for each user by default Key: YARN-222 URL: https://issues.apache.org/jira/browse/YARN-222 Project: Hadoop YARN Issue Type

[jira] [Commented] (YARN-184) Remove unnecessary locking in fair scheduler, and address findbugs excludes.

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

[jira] [Commented] (YARN-184) Remove unnecessary locking in fair scheduler, and address findbugs excludes.

[ https://issues.apache.org/jira/browse/YARN-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499352#comment-13499352 ] Alejandro Abdelnur commented on YARN-184: - Sandy, looks good except for something I'