[jira] [Updated] (YARN-369) Handle ( or throw a proper error when receiving) status updates from application masters that have not registered

[ https://issues.apache.org/jira/browse/YARN-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kapoor updated YARN-369: - Attachment: YARN-369.patch Please code review the patch. Handle ( or throw a

[jira] [Commented] (YARN-369) Handle ( or throw a proper error when receiving) status updates from application masters that have not registered

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

[jira] [Commented] (YARN-227) Application expiration difficult to debug for end-users

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

[jira] [Created] (YARN-452) Deadlock in Resource Manager due to AMResponsePBImpl lock

Devaraj K created YARN-452: -- Summary: Deadlock in Resource Manager due to AMResponsePBImpl lock Key: YARN-452 URL: https://issues.apache.org/jira/browse/YARN-452 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-369) Handle ( or throw a proper error when receiving) status updates from application masters that have not registered

[ https://issues.apache.org/jira/browse/YARN-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13594632#comment-13594632 ] Abhishek Kapoor commented on YARN-369: -- Am working on it. Handle ( or

[jira] [Commented] (YARN-227) Application expiration difficult to debug for end-users

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

[jira] [Commented] (YARN-227) Application expiration difficult to debug for end-users

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

[jira] [Commented] (YARN-369) Handle ( or throw a proper error when receiving) status updates from application masters that have not registered

[ https://issues.apache.org/jira/browse/YARN-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13594702#comment-13594702 ] Abhishek Kapoor commented on YARN-369: -- It looks like the respective change to fix the

[jira] [Commented] (YARN-227) Application expiration difficult to debug for end-users

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

[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=13594767#comment-13594767 ] Arun C Murthy commented on YARN-443: Thomas, wouldn't it be better to come from

[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: hbase-7904-v3.txt Patch v3 allows mapreduce.TestTableMapReduce#testMultiRegionTable to pass on both

[jira] [Commented] (YARN-452) Deadlock in Resource Manager due to AMResponsePBImpl lock

[ https://issues.apache.org/jira/browse/YARN-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13594781#comment-13594781 ] Thomas Graves commented on YARN-452: This looks like a dup of

[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=13594794#comment-13594794 ] Thomas Graves commented on YARN-443: Can you elaborate on your proposal. Are you saying

[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=13594800#comment-13594800 ] Thomas Graves commented on YARN-443: Note the patch attached isn't quite complete

[jira] [Commented] (YARN-369) Handle ( or throw a proper error when receiving) status updates from application masters that have not registered

[ https://issues.apache.org/jira/browse/YARN-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13594827#comment-13594827 ] Abhishek Kapoor commented on YARN-369: -- On further analysis it looks like allocate call

[jira] [Commented] (YARN-417) Add a poller that allows the AM to receive notifications when it is assigned containers

[ https://issues.apache.org/jira/browse/YARN-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13594879#comment-13594879 ] Chris Riccomini commented on YARN-417: -- Hey Bikas, Not sure what you mean here: bq.

[jira] [Commented] (YARN-369) Handle ( or throw a proper error when receiving) status updates from application masters that have not registered

[ https://issues.apache.org/jira/browse/YARN-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13594898#comment-13594898 ] Bikas Saha commented on YARN-369: - The TestRMRestart should not fail because of this fix. Is

[jira] [Commented] (YARN-369) Handle ( or throw a proper error when receiving) status updates from application masters that have not registered

[ https://issues.apache.org/jira/browse/YARN-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13594901#comment-13594901 ] Bikas Saha commented on YARN-369: - The test is failing because of hitting an NPE in the

[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=13594905#comment-13594905 ] Bikas Saha commented on YARN-443: - I like Arun's suggestion of making this process priority

[jira] [Commented] (YARN-417) Add a poller that allows the AM to receive notifications when it is assigned containers

[ https://issues.apache.org/jira/browse/YARN-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13594892#comment-13594892 ] Bikas Saha commented on YARN-417: - No. There is a field in the response thats currently

[jira] [Updated] (YARN-109) .tmp file is not deleted for localized archives

[ https://issues.apache.org/jira/browse/YARN-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-109: --- Assignee: Mayank Bansal .tmp file is not deleted for localized archives

[jira] [Commented] (YARN-429) capacity-scheduler config missing from yarn-test artifact

[ https://issues.apache.org/jira/browse/YARN-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595006#comment-13595006 ] Hitesh Shah commented on YARN-429: -- +1. Looks good. committing shortly.

[jira] [Commented] (YARN-429) capacity-scheduler config missing from yarn-test artifact

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

[jira] [Commented] (YARN-429) capacity-scheduler config missing from yarn-test artifact

[ https://issues.apache.org/jira/browse/YARN-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595027#comment-13595027 ] stack commented on YARN-429: [~hitesh] May we have it in 2.0 hadoop too please?

[jira] [Commented] (YARN-429) capacity-scheduler config missing from yarn-test artifact

[ https://issues.apache.org/jira/browse/YARN-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595030#comment-13595030 ] stack commented on YARN-429: [~hitesh] nvm. just saw the trunk commit... ignore above. Thanks.

[jira] [Updated] (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:all-tabpanel ] Thomas Graves updated YARN-443: --- Attachment: YARN-443.patch complete patch where code is in container-executor.c. Attaching here since

[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=13595063#comment-13595063 ] Thomas Graves commented on YARN-443: Bikas, where is the windows container executor? I

[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=13595071#comment-13595071 ] Bikas Saha commented on YARN-443: - The native binary on windows is called winutils,exe. It

[jira] [Created] (YARN-453) Optimize FS internal data structures

Karthik Kambatla created YARN-453: - Summary: Optimize FS internal data structures Key: YARN-453 URL: https://issues.apache.org/jira/browse/YARN-453 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-417) Add a poller that allows the AM to receive notifications when it is assigned containers

[ https://issues.apache.org/jira/browse/YARN-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13595378#comment-13595378 ] Hitesh Shah commented on YARN-417: -- @Bikas, @Chris, is there a reason as to why all

[jira] [Updated] (YARN-410) New lines in diagnostics for a failed app on the per-application page make it hard to read

[ https://issues.apache.org/jira/browse/YARN-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-410: Fix Version/s: 0.23.7 Thanks, Omkar. I pulled this into branch-0.23. New lines in

[jira] [Updated] (YARN-453) Optimize FS internal data structures

[ https://issues.apache.org/jira/browse/YARN-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-453: -- Component/s: scheduler Optimize FS internal data structures

[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=13595500#comment-13595500 ] Karthik Kambatla commented on YARN-454: --- The code potentially causing that issue is:

[jira] [Updated] (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:all-tabpanel ] Thomas Graves updated YARN-443: --- Attachment: YARN-443.patch I decided to go with the nice method as it should apply across all the

[jira] [Updated] (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:all-tabpanel ] Thomas Graves updated YARN-443: --- Attachment: (was: YARN-443.patch) allow OS scheduling priority of NM to be different than the

[jira] [Updated] (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:all-tabpanel ] Thomas Graves updated YARN-443: --- Attachment: YARN-443-branch-0.23.patch allow OS scheduling priority of NM to be different than

[jira] [Resolved] (YARN-452) Deadlock in Resource Manager due to AMResponsePBImpl lock

[ https://issues.apache.org/jira/browse/YARN-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj K resolved YARN-452. Resolution: Duplicate Deadlock in Resource Manager due to AMResponsePBImpl lock

[jira] [Commented] (YARN-450) Define value for * in the scheduling protocol

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