[jira] [Commented] (YARN-447) applicationComparator improvement for CS

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

[jira] [Commented] (YARN-447) applicationComparator improvement for CS

[ https://issues.apache.org/jira/browse/YARN-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619573#comment-13619573 ] Vinod Kumar Vavilapalli commented on YARN-447: -- Latest patch looks good. +1.

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619578#comment-13619578 ] Bikas Saha commented on YARN-392: - Sorry, I did not see that patch carefully and assumed

[jira] [Commented] (YARN-193) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits

[ https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619580#comment-13619580 ] Hitesh Shah commented on YARN-193: -- {code} +and will get capped to this value. When it

[jira] [Commented] (YARN-447) applicationComparator improvement for CS

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

[jira] [Commented] (YARN-444) Move special container exit codes from YarnConfiguration to API

[ https://issues.apache.org/jira/browse/YARN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619584#comment-13619584 ] Bikas Saha commented on YARN-444: - IMO when the container exits because YARN took some

[jira] [Created] (YARN-527) Local filecache mkdir fails

Knut O. Hellan created YARN-527: --- Summary: Local filecache mkdir fails Key: YARN-527 URL: https://issues.apache.org/jira/browse/YARN-527 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-527) Local filecache mkdir fails

[ https://issues.apache.org/jira/browse/YARN-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut O. Hellan updated YARN-527: Attachment: yarn-site.xml Local filecache mkdir fails ---

[jira] [Commented] (YARN-309) Make RM provide heartbeat interval to NM

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

[jira] [Commented] (YARN-516) TestContainerLocalizer.testContainerLocalizerMain is failing

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

[jira] [Commented] (YARN-524) TestYarnVersionInfo failing if generated properties doesn't include an SVN URL

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

[jira] [Updated] (YARN-525) make CS node-locality-delay refreshable

[ https://issues.apache.org/jira/browse/YARN-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-525: --- Issue Type: Improvement (was: Bug) Summary: make CS node-locality-delay refreshable (was:

[jira] [Created] (YARN-528) Make IDs read only

Robert Joseph Evans created YARN-528: Summary: Make IDs read only Key: YARN-528 URL: https://issues.apache.org/jira/browse/YARN-528 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-528) Make IDs read only

[ https://issues.apache.org/jira/browse/YARN-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans updated YARN-528: - Attachment: YARN-528.txt This patch contains changes to both Map/Reduce IDs as well as

[jira] [Assigned] (YARN-528) Make IDs read only

[ https://issues.apache.org/jira/browse/YARN-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans reassigned YARN-528: Assignee: Robert Joseph Evans Make IDs read only --

[jira] [Commented] (YARN-528) Make IDs read only

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

[jira] [Commented] (YARN-309) Make RM provide heartbeat interval to NM

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

[jira] [Commented] (YARN-516) TestContainerLocalizer.testContainerLocalizerMain is failing

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

[jira] [Commented] (YARN-524) TestYarnVersionInfo failing if generated properties doesn't include an SVN URL

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

[jira] [Commented] (YARN-447) applicationComparator improvement for CS

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

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619778#comment-13619778 ] Thomas Graves commented on YARN-392: Bikas when you say creating an API for blacklisting

[jira] [Commented] (YARN-527) Local filecache mkdir fails

[ https://issues.apache.org/jira/browse/YARN-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619797#comment-13619797 ] Knut O. Hellan commented on YARN-527: - Digging through the code, it looks to me like the

[jira] [Commented] (YARN-309) Make RM provide heartbeat interval to NM

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

[jira] [Commented] (YARN-516) TestContainerLocalizer.testContainerLocalizerMain is failing

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

[jira] [Commented] (YARN-524) TestYarnVersionInfo failing if generated properties doesn't include an SVN URL

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

[jira] [Commented] (YARN-475) Remove ApplicationConstants.AM_APP_ATTEMPT_ID_ENV as it is no longer set in an AM's environment

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

[jira] [Commented] (YARN-447) applicationComparator improvement for CS

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

[jira] [Commented] (YARN-528) Make IDs read only

[ https://issues.apache.org/jira/browse/YARN-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619911#comment-13619911 ] Robert Joseph Evans commented on YARN-528: -- The build failed, because it needs to

[jira] [Updated] (YARN-528) Make IDs read only

[ https://issues.apache.org/jira/browse/YARN-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans updated YARN-528: - Attachment: YARN-528.txt Upmerged Make IDs read only --

[jira] [Commented] (YARN-193) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits

[ https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619957#comment-13619957 ] Zhijie Shen commented on YARN-193: -- {quote} I am not sure if we should allow disabling of

[jira] [Commented] (YARN-528) Make IDs read only

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

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620008#comment-13620008 ] Bikas Saha commented on YARN-392: - Yes YARN-398 but not the proposal currently in there. The

[jira] [Updated] (YARN-122) CompositeService should clone the Configurations it passes to children

[ https://issues.apache.org/jira/browse/YARN-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-122: Priority: Minor (was: Major) CompositeService should clone the Configurations it passes to

[jira] [Updated] (YARN-529) MR app master clean staging dir when reboot command sent from RM while the MR job succeeded

[ https://issues.apache.org/jira/browse/YARN-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jian he updated YARN-529: - Summary: MR app master clean staging dir when reboot command sent from RM while the MR job succeeded (was: IF RM

[jira] [Updated] (YARN-529) MR app master clean staging dir when reboot command sent from RM while the MR job succeeded

[ https://issues.apache.org/jira/browse/YARN-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jian he updated YARN-529: - Description: MR app master will clean staging dir, if the job is already succeeded and asked to reboot. RM will

[jira] [Assigned] (YARN-529) MR app master clean staging dir when reboot command sent from RM while the MR job succeeded

[ https://issues.apache.org/jira/browse/YARN-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jian he reassigned YARN-529: Assignee: jian he MR app master clean staging dir when reboot command sent from RM while the MR job

[jira] [Created] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

Steve Loughran created YARN-530: --- Summary: Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services Key: YARN-530 URL:

[jira] [Assigned] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

[ https://issues.apache.org/jira/browse/YARN-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran reassigned YARN-530: --- Assignee: Steve Loughran Define Service model strictly, implement AbstractService for

[jira] [Resolved] (YARN-121) Yarn services to throw a YarnException on invalid state changs

[ https://issues.apache.org/jira/browse/YARN-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved YARN-121. - Resolution: Duplicate Fix Version/s: 3.0.0 Superceded by YARN-530 Yarn

[jira] [Resolved] (YARN-120) Make yarn-common services robust

[ https://issues.apache.org/jira/browse/YARN-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved YARN-120. - Resolution: Duplicate Fix Version/s: 3.0.0 Superceded by YARN-530 Make

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13620057#comment-13620057 ] Bikas Saha commented on YARN-382: - +1 looks good to me. SchedulerUtils

[jira] [Updated] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

[ https://issues.apache.org/jira/browse/YARN-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-530: Attachment: YARN-117changes.pdf this is an overview of the changes, with explanations

[jira] [Updated] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

[ https://issues.apache.org/jira/browse/YARN-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-530: Attachment: YARN-530.patch This is the subset of YARN-117 for yarn-common Define

[jira] [Commented] (YARN-193) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits

[ https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620066#comment-13620066 ] Bikas Saha commented on YARN-193: - Can we check that we are getting the expected exception

[jira] [Updated] (YARN-117) Enhance YARN service model

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-117: Attachment: YARN-117.patch This is the across-all-yarn-projects patch (plus HADOOP-9447) just to

[jira] [Commented] (YARN-193) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits

[ https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620091#comment-13620091 ] Bikas Saha commented on YARN-193: - Also, why are there so many normalize functions and why

[jira] [Commented] (YARN-529) MR app master clean staging dir when reboot command sent from RM while the MR job succeeded

[ https://issues.apache.org/jira/browse/YARN-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620092#comment-13620092 ] jian he commented on YARN-529: -- several solutions: 1. Let RM accept old attempts. In current

[jira] [Commented] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

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

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13620097#comment-13620097 ] Hudson commented on YARN-382: - Integrated in Hadoop-trunk-Commit #3549 (See

[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 ] Vinod Kumar Vavilapalli updated YARN-382: - Fix Version/s: 2.0.5-beta SchedulerUtils improve way normalizeRequest sets

[jira] [Resolved] (YARN-442) The ID classes should be immutable

[ https://issues.apache.org/jira/browse/YARN-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-442. -- Resolution: Duplicate Assignee: (was: Xuan Gong) YARN-528 is fixing

[jira] [Commented] (YARN-117) Enhance YARN service model

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

[jira] [Commented] (YARN-528) Make IDs read only

[ https://issues.apache.org/jira/browse/YARN-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620170#comment-13620170 ] Vinod Kumar Vavilapalli commented on YARN-528: -- bq. We have no plans to support

[jira] [Commented] (YARN-529) MR app master clean staging dir when reboot command sent from RM while the MR job succeeded

[ https://issues.apache.org/jira/browse/YARN-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620230#comment-13620230 ] Bikas Saha commented on YARN-529: - By 1) you mean let RM accept finishApplicationAttempt()

[jira] [Updated] (YARN-529) Succeeded MR job is retried by RM if finishApplicationMaster() call fails

[ https://issues.apache.org/jira/browse/YARN-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-529: Summary: Succeeded MR job is retried by RM if finishApplicationMaster() call fails (was: Succeeded RM job

[jira] [Updated] (YARN-529) Succeeded RM job is retried by RM if finishApplicationMaster() call fails

[ https://issues.apache.org/jira/browse/YARN-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-529: Summary: Succeeded RM job is retried by RM if finishApplicationMaster() call fails (was: MR app master

[jira] [Updated] (YARN-529) Succeeded MR job is retried by RM if finishApplicationMaster() call fails

[ https://issues.apache.org/jira/browse/YARN-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-529: Issue Type: Improvement (was: Sub-task) Parent: (was: YARN-128) Succeeded MR job is

[jira] [Commented] (YARN-527) Local filecache mkdir fails

[ https://issues.apache.org/jira/browse/YARN-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620239#comment-13620239 ] Vinod Kumar Vavilapalli commented on YARN-527: -- Is there any difference in how

[jira] [Commented] (YARN-101) If the heartbeat message loss, the nodestatus info of complete container will loss too.

[ https://issues.apache.org/jira/browse/YARN-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620261#comment-13620261 ] Xuan Gong commented on YARN-101: 1.Use YarnServerBuilderUtils for constructing

[jira] [Assigned] (YARN-486) Change startContainer NM API to accept Container as a parameter and make ContainerLaunchContext user land

[ https://issues.apache.org/jira/browse/YARN-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reassigned YARN-486: -- Assignee: Xuan Gong (was: Bikas Saha) Change startContainer NM API to accept Container as a

[jira] [Commented] (YARN-528) Make IDs read only

[ https://issues.apache.org/jira/browse/YARN-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620275#comment-13620275 ] Siddharth Seth commented on YARN-528: - Yep, we'll likely only support a single

[jira] [Updated] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats

[ https://issues.apache.org/jira/browse/YARN-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-479: - Attachment: YARN-479.5.patch NM retry behavior for connection to RM should be similar for lost heartbeats

[jira] [Commented] (YARN-101) If the heartbeat message loss, the nodestatus info of complete container will loss too.

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

[jira] [Commented] (YARN-479) NM retry behavior for connection to RM should be similar for lost heartbeats

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

[jira] [Commented] (YARN-528) Make IDs read only

[ https://issues.apache.org/jira/browse/YARN-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620326#comment-13620326 ] Robert Joseph Evans commented on YARN-528: -- I am fine with splitting the MR changes

[jira] [Created] (YARN-532) RMAdminProtocolPBClientImpl should implement Closeable

Siddharth Seth created YARN-532: --- Summary: RMAdminProtocolPBClientImpl should implement Closeable Key: YARN-532 URL: https://issues.apache.org/jira/browse/YARN-532 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-532) RMAdminProtocolPBClientImpl should implement Closeable

[ https://issues.apache.org/jira/browse/YARN-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated YARN-532: Attachment: YARN-532.txt Trivial fix. RMAdminProtocolPBClientImpl should implement

[jira] [Commented] (YARN-528) Make IDs read only

[ https://issues.apache.org/jira/browse/YARN-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620348#comment-13620348 ] Siddharth Seth commented on YARN-528: - bq. I really don't understand how this is

[jira] [Commented] (YARN-532) RMAdminProtocolPBClientImpl should implement Closeable

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

[jira] [Updated] (YARN-193) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits

[ https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-193: - Attachment: YARN-193.12.patch 1. Remove the DISABLE_RESOURCELIMIT_CHECK feature, and its related test

[jira] [Updated] (YARN-467) Jobs fail during resource localization when public distributed-cache hits unix directory limits

[ https://issues.apache.org/jira/browse/YARN-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-467: --- Attachment: yarn-467-20130402.patch Fixing below issues 1) all the formatting issues 2

[jira] [Commented] (YARN-467) Jobs fail during resource localization when public distributed-cache hits unix directory limits

of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12576681/yarn-467-20130402.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 2

[jira] [Commented] (YARN-193) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits

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

[jira] [Updated] (YARN-467) Jobs fail during resource localization when public distributed-cache hits unix directory limits

, yarn-467-20130322.3.patch, yarn-467-20130322.patch, yarn-467-20130325.1.patch, yarn-467-20130325.path, yarn-467-20130328.patch, yarn-467-20130401.patch, yarn-467-20130402.1.patch, yarn-467-20130402.patch If we have multiple jobs which uses distributed cache with small size of files

[jira] [Commented] (YARN-467) Jobs fail during resource localization when public distributed-cache hits unix directory limits

, yarn-467-20130401.patch, yarn-467-20130402.1.patch, yarn-467-20130402.patch If we have multiple jobs which uses distributed cache with small size of files, the directory limit reaches before reaching the cache size and fails to create any directories in file cache (PUBLIC). The jobs start

[jira] [Created] (YARN-533) Pointing to the config property when throwing/logging the config-related exception

Zhijie Shen created YARN-533: Summary: Pointing to the config property when throwing/logging the config-related exception Key: YARN-533 URL: https://issues.apache.org/jira/browse/YARN-533 Project: Hadoop

[jira] [Updated] (YARN-495) Containers are not terminated when the NM is rebooted

[ https://issues.apache.org/jira/browse/YARN-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-495: - Attachment: YARN-495.2.patch Containers are not terminated when the NM is rebooted

[jira] [Commented] (YARN-495) Containers are not terminated when the NM is rebooted

[ https://issues.apache.org/jira/browse/YARN-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620443#comment-13620443 ] Jian He commented on YARN-495: -- Uploaded a patch, change NM behavior from REBOOT to RESYNC when

[jira] [Commented] (YARN-495) Containers are not terminated when the NM is rebooted

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

[jira] [Created] (YARN-534) AM max attempts is not checked when RM restart and try to recover attempts

Jian He created YARN-534: Summary: AM max attempts is not checked when RM restart and try to recover attempts Key: YARN-534 URL: https://issues.apache.org/jira/browse/YARN-534 Project: Hadoop YARN

[jira] [Updated] (YARN-458) Resource manager address must be placed in four different configs

[ https://issues.apache.org/jira/browse/YARN-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-458: Attachment: YARN-458.patch Resource manager address must be placed in four different configs

[jira] [Commented] (YARN-458) Resource manager address must be placed in four different configs

[ https://issues.apache.org/jira/browse/YARN-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620489#comment-13620489 ] Sandy Ryza commented on YARN-458: - Uploaded a patch that adds yarn.resourcemanager.hostname

[jira] [Updated] (YARN-458) YARN daemon addresses must be placed in many different configs

[ https://issues.apache.org/jira/browse/YARN-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-458: Summary: YARN daemon addresses must be placed in many different configs (was: Resource manager address must

[jira] [Updated] (YARN-458) YARN daemon addresses must be placed in many different configs

[ https://issues.apache.org/jira/browse/YARN-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-458: Description: The YARN resourcemanager's address is included in four different configs:

[jira] [Updated] (YARN-458) YARN daemon addresses must be placed in many different configs

[ https://issues.apache.org/jira/browse/YARN-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-458: Affects Version/s: 2.0.3-alpha YARN daemon addresses must be placed in many different configs

[jira] [Updated] (YARN-458) YARN daemon addresses must be placed in many different configs

[ https://issues.apache.org/jira/browse/YARN-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-458: Component/s: resourcemanager nodemanager YARN daemon addresses must be placed in many

[jira] [Commented] (YARN-458) YARN daemon addresses must be placed in many different configs

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

[jira] [Commented] (YARN-467) Jobs fail during resource localization when public distributed-cache hits unix directory limits

-20130322.2.patch, yarn-467-20130322.3.patch, yarn-467-20130322.patch, yarn-467-20130325.1.patch, yarn-467-20130325.path, yarn-467-20130328.patch, yarn-467-20130401.patch, yarn-467-20130402.1.patch, yarn-467-20130402.patch If we have multiple jobs which uses distributed cache with small

[jira] [Updated] (YARN-467) Jobs fail during resource localization when public distributed-cache hits unix directory limits

-20130325.1.patch, yarn-467-20130325.path, yarn-467-20130328.patch, yarn-467-20130401.patch, yarn-467-20130402.1.patch, yarn-467-20130402.2.patch, yarn-467-20130402.patch If we have multiple jobs which uses distributed cache with small size of files, the directory limit reaches before

[jira] [Commented] (YARN-467) Jobs fail during resource localization when public distributed-cache hits unix directory limits

, yarn-467-20130401.patch, yarn-467-20130402.1.patch, yarn-467-20130402.2.patch, yarn-467-20130402.patch If we have multiple jobs which uses distributed cache with small size of files, the directory limit reaches before reaching the cache size and fails to create any directories in file

[jira] [Updated] (YARN-101) If the heartbeat message loss, the nodestatus info of complete container will loss too.

[ https://issues.apache.org/jira/browse/YARN-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-101: --- Attachment: YARN-101.6.patch recreate test case to verify status of all containers in every heartbeat

[jira] [Commented] (YARN-467) Jobs fail during resource localization when public distributed-cache hits unix directory limits

, yarn-467-20130322.2.patch, yarn-467-20130322.3.patch, yarn-467-20130322.patch, yarn-467-20130325.1.patch, yarn-467-20130325.path, yarn-467-20130328.patch, yarn-467-20130401.patch, yarn-467-20130402.1.patch, yarn-467-20130402.2.patch, yarn-467-20130402.patch If we have multiple jobs which

[jira] [Commented] (YARN-101) If the heartbeat message loss, the nodestatus info of complete container will loss too.

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

[jira] [Commented] (YARN-467) Jobs fail during resource localization when public distributed-cache hits unix directory limits

-467-20130325.1.patch, yarn-467-20130325.path, yarn-467-20130328.patch, yarn-467-20130401.patch, yarn-467-20130402.1.patch, yarn-467-20130402.2.patch, yarn-467-20130402.patch If we have multiple jobs which uses distributed cache with small size of files, the directory limit reaches before

[jira] [Commented] (YARN-193) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits

[ https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620638#comment-13620638 ] Bikas Saha commented on YARN-193: - Default value of max-vcores of 32 might be too high. Why

[jira] [Commented] (YARN-193) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits

[ https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620651#comment-13620651 ] Zhijie Shen commented on YARN-193: -- {quote} Default value of max-vcores of 32 might be too