[jira] [Commented] (YARN-443) allow OS scheduling priority of NM to be different than the containers it launches

[ https://issues.apache.org/jira/browse/YARN-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597154#comment-13597154 ] Thomas Graves commented on YARN-443: I intended to leave that log message in there

[jira] [Created] (YARN-459) DefaultContainerExecutor doesn't log stderr from container launch

Thomas Graves created YARN-459: -- Summary: DefaultContainerExecutor doesn't log stderr from container launch Key: YARN-459 URL: https://issues.apache.org/jira/browse/YARN-459 Project: Hadoop YARN

[jira] [Commented] (YARN-443) allow OS scheduling priority of NM to be different than the containers it launches

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

[jira] [Moved] (YARN-460) CS user left in list of active users for the queue even when application finished

[ https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves moved MAPREDUCE-5054 to YARN-460: --- Component/s: (was: capacity-sched)

[jira] [Commented] (YARN-460) CS user left in list of active users for the queue even when application finished

[ https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597237#comment-13597237 ] Thomas Graves commented on YARN-460: Just for reference the RM log shows the application

[jira] [Commented] (YARN-460) CS user left in list of active users for the queue even when application finished

[ https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597281#comment-13597281 ] Thomas Graves commented on YARN-460: Note that this is due to the fact that

[jira] [Commented] (YARN-459) DefaultContainerExecutor doesn't log stderr from container launch

[ https://issues.apache.org/jira/browse/YARN-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597388#comment-13597388 ] Chris Nauroth commented on YARN-459: +1 for fixing this. It would be very helpful for

[jira] [Commented] (YARN-449) MRAppMaster classpath not set properly for unit tests in downstream projects

[ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597392#comment-13597392 ] Ted Yu commented on YARN-449: - TestRowCounter failed with hadoop 2.0.2-alpha on the above

[jira] [Commented] (YARN-459) DefaultContainerExecutor doesn't log stderr from container launch

[ https://issues.apache.org/jira/browse/YARN-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597421#comment-13597421 ] Sandy Ryza commented on YARN-459: - This looks related to Koji's patch for MAPREDUCE-3688

[jira] [Commented] (YARN-378) ApplicationMaster retry times should be set by Client

[ https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597428#comment-13597428 ] Robert Joseph Evans commented on YARN-378: -- From a quick look it seems OK. It

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

[ https://issues.apache.org/jira/browse/YARN-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597508#comment-13597508 ] Robert Joseph Evans commented on YARN-237: -- I have a few more comments. It is

[jira] [Commented] (YARN-461) RMAppManager accepts apps with empty string names and queues

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

[jira] [Created] (YARN-462) Project Parameter for Chargeback

Kendall Thrapp created YARN-462: --- Summary: Project Parameter for Chargeback Key: YARN-462 URL: https://issues.apache.org/jira/browse/YARN-462 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-462) Project Parameter for Chargeback

[ https://issues.apache.org/jira/browse/YARN-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kendall Thrapp updated YARN-462: Issue Type: New Feature (was: Improvement) Project Parameter for Chargeback

[jira] [Created] (YARN-463) Show explicitly excluded nodes on the UI

Vinod Kumar Vavilapalli created YARN-463: Summary: Show explicitly excluded nodes on the UI Key: YARN-463 URL: https://issues.apache.org/jira/browse/YARN-463 Project: Hadoop YARN

[jira] [Commented] (YARN-463) Show explicitly excluded nodes on the UI

[ https://issues.apache.org/jira/browse/YARN-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597529#comment-13597529 ] Jason Lowe commented on YARN-463: - On a similar note, should we also be listing nodes that

[jira] [Commented] (YARN-461) RMAppManager accepts apps with empty string names and queues

[ https://issues.apache.org/jira/browse/YARN-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597584#comment-13597584 ] Arun C Murthy commented on YARN-461: Not sure this is correct. The default value for

[jira] [Commented] (YARN-461) RMAppManager accepts apps with empty string names and queues

[ https://issues.apache.org/jira/browse/YARN-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597586#comment-13597586 ] Arun C Murthy commented on YARN-461: Same for app name. RMAppManager

[jira] [Updated] (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 ] Xuan Gong updated YARN-196: --- Attachment: YARN-196.9.patch Nodemanager if started before starting Resource manager is getting

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13597609#comment-13597609 ] Hadoop QA commented on YARN-196: {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-460) CS user left in list of active users for the queue even when application finished

[ https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597612#comment-13597612 ] Thomas Graves commented on YARN-460: Note that is the branch-0.23 patch. Working on

[jira] [Updated] (YARN-382) SchedulerUtils improve way normalizeRequest sets the resource capabilities

[ https://issues.apache.org/jira/browse/YARN-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-382: - Attachment: YARN-382_1.patch YARN-382_demo.patch I've investigated the method of embedding

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

[ https://issues.apache.org/jira/browse/YARN-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597628#comment-13597628 ] jian he commented on YARN-237: -- I agree that sessionStorage makes more sense here, it cleans up

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

[ https://issues.apache.org/jira/browse/YARN-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jian he updated YARN-237: - Attachment: YARN-237.v3.patch Refreshing the RM page forgets how many rows I had in my Datatables

[jira] [Updated] (YARN-460) CS user left in list of active users for the queue even when application finished

[ https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-460: --- Attachment: YARN-460-branch-0.23.patch CS user left in list of active users for the queue even

[jira] [Updated] (YARN-460) CS user left in list of active users for the queue even when application finished

[ https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-460: --- Attachment: YARN-460.patch updated patch for trunk/branch-2. CS user left in list

[jira] [Created] (YARN-464) RM should inform AM how many AM retires it has

Zhijie Shen created YARN-464: Summary: RM should inform AM how many AM retires it has Key: YARN-464 URL: https://issues.apache.org/jira/browse/YARN-464 Project: Hadoop YARN Issue Type:

[jira] [Updated] (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 ] Xuan Gong updated YARN-196: --- Attachment: YARN-196.10.patch Fix format issue Nodemanager if started before starting

[jira] [Commented] (YARN-460) CS user left in list of active users for the queue even when application finished

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

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13597659#comment-13597659 ] Hadoop QA commented on YARN-196: {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-449) MRAppMaster classpath not set properly for unit tests in downstream projects

[ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated YARN-449: Attachment: 7904-v5.txt Patch v5 was suggested by Sid. MRAppMaster classpath not set properly for

[jira] [Updated] (YARN-378) ApplicationMaster retry times should be set by Client

[ https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-378: - Attachment: YARN-378_2.patch Thanks, Robert! I've addressed your comments in the newer patch. In

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

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

[jira] [Commented] (YARN-378) ApplicationMaster retry times should be set by Client

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

[jira] [Commented] (YARN-461) RMAppManager accepts apps with empty string names and queues

[ https://issues.apache.org/jira/browse/YARN-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597789#comment-13597789 ] Sandy Ryza commented on YARN-461: - My thinking was that a queue name of is most likely to

[jira] [Commented] (YARN-454) FS could wait until next NODE_UPDATE event to schedule a reserved container

[ https://issues.apache.org/jira/browse/YARN-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597791#comment-13597791 ] Karthik Kambatla commented on YARN-454: --- Spoke to Sandy offline; he is right - this is

[jira] [Resolved] (YARN-454) FS could wait until next NODE_UPDATE event to schedule a reserved container

[ https://issues.apache.org/jira/browse/YARN-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-454. --- Resolution: Invalid FS could wait until next NODE_UPDATE event to schedule a reserved

[jira] [Commented] (YARN-461) RMAppManager accepts apps with empty string names and queues

[ https://issues.apache.org/jira/browse/YARN-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597798#comment-13597798 ] Arun C Murthy commented on YARN-461: If the user specifically set the queue name to be

[jira] [Commented] (YARN-461) RMAppManager accepts apps with empty string names and queues

[ https://issues.apache.org/jira/browse/YARN-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597817#comment-13597817 ] Karthik Kambatla commented on YARN-461: --- Throwing an error seems reasonable to me.

[jira] [Commented] (YARN-462) Project Parameter for Chargeback

[ https://issues.apache.org/jira/browse/YARN-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597818#comment-13597818 ] Karthik Kambatla commented on YARN-462: --- Interesting idea, Kendall. Just so I

[jira] [Commented] (YARN-462) Project Parameter for Chargeback

[ https://issues.apache.org/jira/browse/YARN-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597822#comment-13597822 ] Karthik Kambatla commented on YARN-462: --- I might have jumped the gun there with my

[jira] [Commented] (YARN-461) RMAppManager accepts apps with empty string names and queues

[ https://issues.apache.org/jira/browse/YARN-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597836#comment-13597836 ] Sandy Ryza commented on YARN-461: - Sorry, misextrapolated your first comment, that seems

[jira] [Updated] (YARN-378) ApplicationMaster retry times should be set by Client

[ https://issues.apache.org/jira/browse/YARN-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-378: - Attachment: YARN-378_3.patch Add timeouts for the two newly added test cases.

[jira] [Commented] (YARN-378) ApplicationMaster retry times should be set by Client

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