[jira] [Updated] (YARN-18) Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology

[ https://issues.apache.org/jira/browse/YARN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-18: --- Attachment: YARN-18-v5.patch Make locatlity in YARN's container assignment and task scheduling pluggable

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13613676#comment-13613676 ] Hudson commented on YARN-109: - Integrated in Hadoop-Yarn-trunk #167 (See

[jira] [Commented] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly

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

[jira] [Commented] (YARN-497) Yarn unmanaged-am launcher jar does not define a main class in its manifest

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

[jira] [Commented] (YARN-469) Make scheduling mode in FS pluggable

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

[jira] [Commented] (YARN-439) Flatten NodeHeartbeatResponse

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

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13613732#comment-13613732 ] Hudson commented on YARN-109: - Integrated in Hadoop-Hdfs-0.23-Build #565 (See

[jira] [Commented] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly

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

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13613749#comment-13613749 ] Hudson commented on YARN-109: - Integrated in Hadoop-Hdfs-trunk #1356 (See

[jira] [Commented] (YARN-497) Yarn unmanaged-am launcher jar does not define a main class in its manifest

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

[jira] [Commented] (YARN-71) Ensure/confirm that the NodeManager cleans up local-dirs on restart

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

[jira] [Commented] (YARN-439) Flatten NodeHeartbeatResponse

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

[jira] [Commented] (YARN-469) Make scheduling mode in FS pluggable

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

[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=13613757#comment-13613757 ] Hudson commented on YARN-378: - Integrated in Hadoop-Hdfs-trunk #1356 (See

[jira] [Commented] (YARN-498) Unmanaged AM launcher does not set various constants in env for an AM, also does not handle failed AMs properly

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

[jira] [Commented] (YARN-469) Make scheduling mode in FS pluggable

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

[jira] [Commented] (YARN-497) Yarn unmanaged-am launcher jar does not define a main class in its manifest

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

[jira] [Commented] (YARN-439) Flatten NodeHeartbeatResponse

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

[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=13614036#comment-13614036 ] Robert Joseph Evans commented on YARN-378: -- Hitesh and Vinod, It is not a big

[jira] [Commented] (YARN-7) Add support for DistributedShell to ask for CPUs along with memory

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

[jira] [Assigned] (YARN-7) Add support for DistributedShell to ask for CPUs along with memory

[ https://issues.apache.org/jira/browse/YARN-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-7: - Assignee: Junping Du Add support for DistributedShell to ask for CPUs along with memory

[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.6.patch Based on @Hitesh's previous patch, I've made the following changes in the

[jira] [Commented] (YARN-18) Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology

[ https://issues.apache.org/jira/browse/YARN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614355#comment-13614355 ] Arun C Murthy commented on YARN-18: --- Sorry, I'm just getting to this. This is a lot to

[jira] [Assigned] (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 reassigned YARN-101: -- Assignee: Xuan Gong If the heartbeat message loss, the nodestatus info of complete container

[jira] [Commented] (YARN-440) Flatten RegisterNodeManagerResponse

[ https://issues.apache.org/jira/browse/YARN-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614381#comment-13614381 ] Siddharth Seth commented on YARN-440: - +1. Committing. Flatten

[jira] [Assigned] (YARN-98) NM Application invalid state transition on reboot command from RM

[ https://issues.apache.org/jira/browse/YARN-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] omkar vinit joshi reassigned YARN-98: - Assignee: omkar vinit joshi NM Application invalid state transition on reboot command

[jira] [Updated] (YARN-474) CapacityScheduler does not activate applications when configuration is refreshed

[ https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-474: - Attachment: YARN-474.2.patch Separate the fix for the specific problem of YARN-474 and that of YARN-209,

[jira] [Updated] (YARN-209) Capacity scheduler can leave application in pending state

[ https://issues.apache.org/jira/browse/YARN-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-209: - Attachment: YARN-209.3.patch Extract the fixing code specifically for this issue from YARN-474, to make

[jira] [Commented] (YARN-112) Race in localization can cause containers to fail

[ https://issues.apache.org/jira/browse/YARN-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614402#comment-13614402 ] Robert Joseph Evans commented on YARN-112: -- I am not really sure that we fixed the

[jira] [Commented] (YARN-209) Capacity scheduler can leave application in pending state

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

[jira] [Commented] (YARN-474) CapacityScheduler does not activate applications when configuration is refreshed

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

[jira] [Updated] (YARN-172) AM logs link in RM ui redirects back to RM if AM not started

[ https://issues.apache.org/jira/browse/YARN-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-172: - Labels: usability (was: ) AM logs link in RM ui redirects back to RM if AM

[jira] [Updated] (YARN-20) More information for yarn.resourcemanager.webapp.address in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-20: Component/s: documentation More information for

[jira] [Updated] (YARN-432) Documentation for Log Aggregation and log retrieval.

[ https://issues.apache.org/jira/browse/YARN-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-432: - Component/s: documentation Documentation for Log Aggregation and log

[jira] [Commented] (YARN-24) Nodemanager fails to start if log aggregation enabled and namenode unavailable

[ https://issues.apache.org/jira/browse/YARN-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614486#comment-13614486 ] Sandy Ryza commented on YARN-24: Thinking about this a little more, I didn't see a strong

[jira] [Commented] (YARN-503) DelegationTokens will be renewed forever if multiple jobs share tokens and the first one sets JOB_CANCEL_DELEGATION_TOKEN to false

[ https://issues.apache.org/jira/browse/YARN-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614502#comment-13614502 ] Daryn Sharp commented on YARN-503: -- bq. Will the case of MR actions be an issue? that the

[jira] [Created] (YARN-509) ResourceTrackerPB misses KerberosInfo annotation which renders YARN unusable on secure clusters

Konstantin Boudnik created YARN-509: --- Summary: ResourceTrackerPB misses KerberosInfo annotation which renders YARN unusable on secure clusters Key: YARN-509 URL: https://issues.apache.org/jira/browse/YARN-509

[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.7.patch Clean up the warnings in TestRMAppAttemptTransitions and fix the broken test

[jira] [Commented] (YARN-112) Race in localization can cause containers to fail

[ https://issues.apache.org/jira/browse/YARN-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614650#comment-13614650 ] Vinod Kumar Vavilapalli commented on YARN-112: -- Bobby, I too have seen in large

[jira] [Commented] (YARN-112) Race in localization can cause containers to fail

[ https://issues.apache.org/jira/browse/YARN-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614654#comment-13614654 ] Vinod Kumar Vavilapalli commented on YARN-112: -- bq. We don't see the random

[jira] [Updated] (YARN-209) Capacity scheduler doesn't trigger app-activation after adding nodes

[ https://issues.apache.org/jira/browse/YARN-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-209: - Summary: Capacity scheduler doesn't trigger app-activation after adding nodes

[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.2.patch 1. recreate the patch based on the latest trunk version 2. add new testcase to

[jira] [Commented] (YARN-18) Make locatlity in YARN's container assignment and task scheduling pluggable for other deployment topology

[ https://issues.apache.org/jira/browse/YARN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614675#comment-13614675 ] Junping Du commented on YARN-18: Thanks Arun and Luke for comments and review. [~acmurthy],

[jira] [Commented] (YARN-509) ResourceTrackerPB misses KerberosInfo annotation which renders YARN unusable on secure clusters

[ https://issues.apache.org/jira/browse/YARN-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614710#comment-13614710 ] Roman Shaposhnik commented on YARN-509: --- This is from Bigtop testing so I can make the

[jira] [Created] (YARN-510) Writing Yarn Applications documentation should be changed to signify use of of fully qualified paths when localizing resources

Hitesh Shah created YARN-510: Summary: Writing Yarn Applications documentation should be changed to signify use of of fully qualified paths when localizing resources Key: YARN-510 URL:

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

[ https://issues.apache.org/jira/browse/YARN-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-309: --- Attachment: YARN-309.4.patch 1. create new contents in YarnConfiguration, to set default value 2. Everytime

[jira] [Commented] (YARN-499) On container failure, include last n lines of logs in diagnostics

[ https://issues.apache.org/jira/browse/YARN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614738#comment-13614738 ] Sandy Ryza commented on YARN-499: - Ravi, The idea of putting the app master in a big

[jira] [Updated] (YARN-499) On container failure, include last n lines of logs in diagnostics

[ https://issues.apache.org/jira/browse/YARN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-499: Attachment: YARN-499.patch On container failure, include last n lines of logs in diagnostics

[jira] [Commented] (YARN-499) On container failure, include last n lines of logs in diagnostics

[ https://issues.apache.org/jira/browse/YARN-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614752#comment-13614752 ] Sandy Ryza commented on YARN-499: - Uploaded a patch that uses tee to send the standard out

[jira] [Commented] (YARN-112) Race in localization can cause containers to fail

[ https://issues.apache.org/jira/browse/YARN-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614755#comment-13614755 ] omkar vinit joshi commented on YARN-112: Vinod's suggestion looks good to me and it

[jira] [Updated] (YARN-112) Race in localization can cause containers to fail

[ https://issues.apache.org/jira/browse/YARN-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] omkar vinit joshi updated YARN-112: --- Attachment: yarn-112-20130326.patch Race in localization can cause containers to fail

[jira] [Updated] (YARN-474) CapacityScheduler does not activate applications when maximum-am-resource-percent configuration is refreshed

[ https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-474: - Attachment: YARN-474.3.patch @Vinod's comments are addressed the newest patch. In addition, I've tested

[jira] [Commented] (YARN-440) Flatten RegisterNodeManagerResponse

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

[jira] [Commented] (YARN-209) Capacity scheduler doesn't trigger app-activation after adding nodes

[ https://issues.apache.org/jira/browse/YARN-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614819#comment-13614819 ] Bikas Saha commented on YARN-209: - Patch looks good overall. I dont quite see what

[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=13614820#comment-13614820 ] Hadoop QA commented on YARN-309: {color:red}-1 overall{color}. Here are the results of

[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=13614833#comment-13614833 ] Bikas Saha commented on YARN-193: - I am not sure if the normalization errors should reach

[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=13614847#comment-13614847 ] Xuan Gong commented on YARN-309: Test case fails because of localhost binding problem. aused

[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=13614848#comment-13614848 ] Xuan Gong commented on YARN-309: And it is not introduced by this patch.

[jira] [Commented] (YARN-499) On container failure, include last n lines of logs in diagnostics

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

[jira] [Commented] (YARN-24) Nodemanager fails to start if log aggregation enabled and namenode unavailable

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

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

[jira] [Commented] (YARN-24) Nodemanager fails to start if log aggregation enabled and namenode unavailable

[ https://issues.apache.org/jira/browse/YARN-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614873#comment-13614873 ] Sandy Ryza commented on YARN-24: Verified the updated patch on a pseudo-distributed cluster

[jira] [Commented] (YARN-474) CapacityScheduler does not activate applications when maximum-am-resource-percent configuration is refreshed

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

[jira] [Commented] (YARN-474) CapacityScheduler does not activate applications when maximum-am-resource-percent configuration is refreshed

[ https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614886#comment-13614886 ] Vinod Kumar Vavilapalli commented on YARN-474: -- The latest patch looks good, I

[jira] [Commented] (YARN-474) CapacityScheduler does not activate applications when maximum-am-resource-percent configuration is refreshed

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

[jira] [Commented] (YARN-157) The option shell_command and shell_script have conflict

[ https://issues.apache.org/jira/browse/YARN-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614922#comment-13614922 ] rainy Yu commented on YARN-157: --- I can't commit Attachments. My patch is: Index:

[jira] [Commented] (YARN-112) Race in localization can cause containers to fail

of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12575629/yarn-112-20130326.patch against trunk revision . {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-YARN-Build/614//console

[jira] [Updated] (YARN-209) Capacity scheduler doesn't trigger app-activation after adding nodes

[ https://issues.apache.org/jira/browse/YARN-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-209: - Attachment: YARN-209.4.patch The log statement is removed and testActivatingPendingApplication is moved to

[jira] [Commented] (YARN-209) Capacity scheduler doesn't trigger app-activation after adding nodes

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

[jira] [Commented] (YARN-474) CapacityScheduler does not activate applications when maximum-am-resource-percent configuration is refreshed

[ https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614961#comment-13614961 ] Konstantin Boudnik commented on YARN-474: - It seems that this commit has broken the

[jira] [Commented] (YARN-474) CapacityScheduler does not activate applications when maximum-am-resource-percent configuration is refreshed

[ https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13614962#comment-13614962 ] Konstantin Boudnik commented on YARN-474: - Here's the error message: {noformat}