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

[ https://issues.apache.org/jira/browse/YARN-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nemon lou updated YARN-447: --- Attachment: YARN-447-trunk.patch Patch rebased. applicationComparator improvement for CS

[jira] [Commented] (YARN-291) Dynamic resource configuration on NM

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618681#comment-13618681 ] Bikas Saha commented on YARN-291: - bq. because NM doesn't really care about what resource it

[jira] [Commented] (YARN-291) Dynamic resource configuration on NM

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618697#comment-13618697 ] Luke Lu commented on YARN-291: -- bq. The NM is the node controller and responsible for managing

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

[jira] [Commented] (YARN-311) Dynamic node resource configuration on RM with JMX interface

[ https://issues.apache.org/jira/browse/YARN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618705#comment-13618705 ] Junping Du commented on YARN-311: - Hi Arun, I understand your concern especially in case

[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=13618735#comment-13618735 ] Hudson commented on YARN-475: - Integrated in Hadoop-Yarn-trunk #172 (See

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

Steve Loughran created YARN-524: --- Summary: TestYarnVersionInfo failing if generated properties doesn't include an SVN URL Key: YARN-524 URL: https://issues.apache.org/jira/browse/YARN-524 Project:

[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=13618756#comment-13618756 ] Steve Loughran commented on YARN-524: - I have a {{yarn-version-info.properties}} file of

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

[jira] [Commented] (YARN-515) Node Manager not getting the master key

[ https://issues.apache.org/jira/browse/YARN-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618784#comment-13618784 ] Robert Joseph Evans commented on YARN-515: -- Having people always test the patches

[jira] [Updated] (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:all-tabpanel ] Steve Loughran updated YARN-524: Attachment: YARN-524.patch replaces with check for nullness, not != unknown

[jira] [Commented] (YARN-449) HBase test failures when running against Hadoop 2

[ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618891#comment-13618891 ] Ted Yu commented on YARN-449: - Based on

[jira] [Assigned] (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:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-524: Assignee: Steve Loughran TestYarnVersionInfo failing if generated

[jira] [Assigned] (YARN-457) Setting updated nodes from null to null causes NPE in AMResponsePBImpl

[ https://issues.apache.org/jira/browse/YARN-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-457: Assignee: Kenji Kikushima Kenji, assigning this to you. In future, it will

[jira] [Updated] (YARN-457) Setting updated nodes from null to null causes NPE in AllocateResponsePBImpl

[ https://issues.apache.org/jira/browse/YARN-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-457: - Summary: Setting updated nodes from null to null causes NPE in

[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=13618938#comment-13618938 ] Sandy Ryza commented on YARN-444: - My thinking behind the plurals was that using the

[jira] [Commented] (YARN-366) Add a tracing async dispatcher to simplify debugging

[ https://issues.apache.org/jira/browse/YARN-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618943#comment-13618943 ] Sandy Ryza commented on YARN-366: - The test failures appear to be unrelated. The findbugs

[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_2.patch Make patch against the latest trunk, and add the comment suggested by Bikas.

[jira] [Commented] (YARN-515) Node Manager not getting the master key

[ https://issues.apache.org/jira/browse/YARN-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13618985#comment-13618985 ] Siddharth Seth commented on YARN-515: - Missed this while reviewing YARN-440... also in

[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=13618991#comment-13618991 ] Bikas Saha commented on YARN-444: - You can look QueueState, YarnApplicationState, NodeState,

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13618997#comment-13618997 ] Siddharth Seth commented on YARN-467: - bq. Another thing I've been looking hard is to

[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=13619005#comment-13619005 ] Alejandro Abdelnur commented on YARN-524: - Where is yarn version info being used? I

[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=13619028#comment-13619028 ] Chris Nauroth commented on YARN-524: {quote} we should use the common's version info

[jira] [Updated] (YARN-412) FifoScheduler incorrectly checking for node locality

[ https://issues.apache.org/jira/browse/YARN-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Hoover updated YARN-412: -- Attachment: (was: YARN-412.patch) FifoScheduler incorrectly checking for node locality

[jira] [Updated] (YARN-412) FifoScheduler incorrectly checking for node locality

[ https://issues.apache.org/jira/browse/YARN-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Hoover updated YARN-412: -- Attachment: (was: YARN-412.patch) FifoScheduler incorrectly checking for node locality

[jira] [Updated] (YARN-412) FifoScheduler incorrectly checking for node locality

[ https://issues.apache.org/jira/browse/YARN-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Hoover updated YARN-412: -- Attachment: (was: YARN-412.patch) FifoScheduler incorrectly checking for node locality

[jira] [Updated] (YARN-412) FifoScheduler incorrectly checking for node locality

[ https://issues.apache.org/jira/browse/YARN-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Hoover updated YARN-412: -- Attachment: YARN-412.patch Regenerated patch to svn version 1463033 FifoScheduler

[jira] [Commented] (YARN-412) FifoScheduler incorrectly checking for node locality

[ https://issues.apache.org/jira/browse/YARN-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619047#comment-13619047 ] Roger Hoover commented on YARN-412: --- [~acmurthy] OK. I've regenerated the patch based on

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

[jira] [Commented] (YARN-291) Dynamic resource configuration on NM

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619059#comment-13619059 ] Alejandro Abdelnur commented on YARN-291: - +1 on the idea of dynamic resource

[jira] [Commented] (YARN-412) FifoScheduler incorrectly checking for node locality

[ https://issues.apache.org/jira/browse/YARN-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619064#comment-13619064 ] Hadoop QA commented on YARN-412: {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=13619111#comment-13619111 ] Zhijie Shen commented on YARN-193: -- @Bikas {quote} This and others like it are

[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=13619116#comment-13619116 ] Zhijie Shen commented on YARN-193: -- @Bikas, Sorry, I didn't complete the last comment but

[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=13619136#comment-13619136 ] Sandy Ryza commented on YARN-392: - It seems like we have two slightly different proposals,

[jira] [Resolved] (YARN-449) HBase test failures when running against Hadoop 2

[ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth resolved YARN-449. - Resolution: Fixed Fix Version/s: 2.0.4-alpha Summarizing for reference, and closing this

[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=13619151#comment-13619151 ] Sandy Ryza commented on YARN-444: - Ok, I am convinced. Uploading new patch with the change.

[jira] [Updated] (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:all-tabpanel ] Sandy Ryza updated YARN-444: Attachment: YARN-444-1.patch Move special container exit codes from YarnConfiguration to API

[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=13619154#comment-13619154 ] Steve Loughran commented on YARN-524: - committed TestYarnVersionInfo

[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=13619161#comment-13619161 ] Hudson commented on YARN-524: - Integrated in Hadoop-trunk-Commit #3543 (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=13619200#comment-13619200 ] Hadoop QA commented on YARN-444: {color:red}-1 overall{color}. Here are the results of

[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=13619203#comment-13619203 ] Sandy Ryza commented on YARN-444: - Test failure is unrelated Move special

[jira] [Updated] (YARN-291) Dynamic resource configuration

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Lu updated YARN-291: - Summary: Dynamic resource configuration (was: Dynamic resource configuration on NM) bq. I have concerns on

[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.11.patch Make RM provide heartbeat interval to NM

[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=13619295#comment-13619295 ] Xuan Gong commented on YARN-309: 1. add new java file

[jira] [Commented] (YARN-291) Dynamic resource configuration

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619298#comment-13619298 ] Alejandro Abdelnur commented on YARN-291: - bq. How so? In fact ... Changes in NM

[jira] [Commented] (YARN-449) HBase test failures when running against Hadoop 2

[ https://issues.apache.org/jira/browse/YARN-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619301#comment-13619301 ] Vinod Kumar Vavilapalli commented on YARN-449: -- bq. I would not build any

[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-20130401.patch Fixing all the comments. Keeping default value for max

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

[jira] [Commented] (YARN-291) Dynamic resource configuration

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619374#comment-13619374 ] Luke Lu commented on YARN-291: -- bq. Changes in NM capacity triggered from outside of the

[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/12576466/yarn-467-20130401.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] [Assigned] (YARN-516) TestContainerLocalizer.testContainerLocalizerMain is failing

[ https://issues.apache.org/jira/browse/YARN-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-516: Assignee: Andrew Wang (was: Vinod Kumar Vavilapalli)

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

[ https://issues.apache.org/jira/browse/YARN-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-516: - Attachment: YARN-516.txt Attaching Andrew's patch from HADOOP-9357. I am +1, will

[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.10.patch I've done the following changes in the newest patch: 1. Undo the

[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.11.patch Clean up one unnecessary import as well.

[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=13619417#comment-13619417 ] Hudson commented on YARN-309: - Integrated in Hadoop-trunk-Commit #3545 (See

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

[jira] [Created] (YARN-525) yarn.scheduler.capacity.node-locality-delay doesn't change with rmadmin -refreshQueues

Thomas Graves created YARN-525: -- Summary: yarn.scheduler.capacity.node-locality-delay doesn't change with rmadmin -refreshQueues Key: YARN-525 URL: https://issues.apache.org/jira/browse/YARN-525

[jira] [Updated] (YARN-465) fix coverage org.apache.hadoop.yarn.server.webproxy

[ https://issues.apache.org/jira/browse/YARN-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-465: - Issue Type: Sub-task (was: Test) Parent: YARN-526 fix coverage

[jira] [Created] (YARN-526) [Umbrella] Improve test coverage in YARN

Vinod Kumar Vavilapalli created YARN-526: Summary: [Umbrella] Improve test coverage in YARN Key: YARN-526 URL: https://issues.apache.org/jira/browse/YARN-526 Project: Hadoop YARN

[jira] [Updated] (YARN-425) coverage fix for yarn api

[ https://issues.apache.org/jira/browse/YARN-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-425: - Issue Type: Sub-task (was: Test) Parent: YARN-526 coverage fix for

[jira] [Updated] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

[ https://issues.apache.org/jira/browse/YARN-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-427: - Issue Type: Sub-task (was: Test) Parent: YARN-526 Coverage fix for

[jira] [Updated] (YARN-478) fix coverage org.apache.hadoop.yarn.webapp.log

[ https://issues.apache.org/jira/browse/YARN-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-478: - Issue Type: Sub-task (was: Test) Parent: YARN-526 fix coverage

[jira] [Assigned] (YARN-427) Coverage fix for org.apache.hadoop.yarn.server.api.*

[ https://issues.apache.org/jira/browse/YARN-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-427: Assignee: Aleksey Gorshkov Coverage fix for

[jira] [Assigned] (YARN-478) fix coverage org.apache.hadoop.yarn.webapp.log

[ https://issues.apache.org/jira/browse/YARN-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-478: Assignee: Aleksey Gorshkov fix coverage

[jira] [Updated] (YARN-480) fix coverage org.apache.hadoop.yarn.server.resourcemanager.api.*

[ https://issues.apache.org/jira/browse/YARN-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-480: - Issue Type: Sub-task (was: Test) Parent: YARN-526 fix coverage

[jira] [Assigned] (YARN-468) coverage fix for org.apache.hadoop.yarn.server.webproxy.amfilter

[ https://issues.apache.org/jira/browse/YARN-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-468: Assignee: Aleksey Gorshkov coverage fix for

[jira] [Updated] (YARN-468) coverage fix for org.apache.hadoop.yarn.server.webproxy.amfilter

[ https://issues.apache.org/jira/browse/YARN-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-468: - Issue Type: Sub-task (was: Test) Parent: YARN-526 coverage fix for

[jira] [Updated] (YARN-204) test coverage for org.apache.hadoop.tools

[ https://issues.apache.org/jira/browse/YARN-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-204: - Issue Type: Sub-task (was: Bug) Parent: YARN-526 test coverage for

[jira] [Updated] (YARN-186) Coverage fixing LinuxContainerExecutor

[ https://issues.apache.org/jira/browse/YARN-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-186: - Issue Type: Sub-task (was: Test) Parent: YARN-526 Coverage fixing

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

[ https://issues.apache.org/jira/browse/YARN-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-188: - Issue Type: Sub-task (was: Test) Parent: YARN-526 Coverage fixing

[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=13619547#comment-13619547 ] Hudson commented on YARN-516: - Integrated in Hadoop-trunk-Commit #3546 (See