[jira] [Created] (YARN-2113) CS Preemption should respect user-limits

Vinod Kumar Vavilapalli created YARN-2113: - Summary: CS Preemption should respect user-limits Key: YARN-2113 URL: https://issues.apache.org/jira/browse/YARN-2113 Project: Hadoop YARN

[jira] [Commented] (YARN-2041) Hard to co-locate MR2 and Spark jobs on the same cluster in YARN

[ https://issues.apache.org/jira/browse/YARN-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012134#comment-14012134 ] Nishkam Ravi commented on YARN-2041: Sure. There seem to be multiple issues. Two seem

[jira] [Updated] (YARN-2098) App priority support in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2098: -- Attachment: YARN-2098.patch App priority support in Fair Scheduler --

[jira] [Assigned] (YARN-596) Use scheduling policies throughout the queue hierarchy to decide which containers to preempt

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan reassigned YARN-596: Assignee: Wei Yan (was: Sandy Ryza) Use scheduling policies throughout the queue hierarchy to decide which

[jira] [Updated] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Tian updated YARN-2083: -- Attachment: YARN-2083.patch In fair scheduler, Queue should not been assigned more containers when its

[jira] [Updated] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Tian updated YARN-2083: -- Attachment: (was: YARN-2083.patch) In fair scheduler, Queue should not been assigned more containers when

[jira] [Commented] (YARN-2098) App priority support in Fair Scheduler

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

[jira] [Commented] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

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

[jira] [Commented] (YARN-1338) Recover localized resource cache state upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012235#comment-14012235 ] Junping Du commented on YARN-1338: -- bq. Good point. I added shutdown code that removes the

[jira] [Commented] (YARN-596) Use scheduling policies throughout the queue hierarchy to decide which containers to preempt

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

[jira] [Commented] (YARN-2107) Refactor timeline classes into server.timeline package

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

[jira] [Commented] (YARN-2107) Refactor timeline classes into server.timeline package

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

[jira] [Commented] (YARN-1972) Implement secure Windows Container Executor

[ https://issues.apache.org/jira/browse/YARN-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012407#comment-14012407 ] Remus Rusanu commented on YARN-1972: Some responses in the mean-while, before I finish

[jira] [Commented] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012444#comment-14012444 ] Tsuyoshi OZAWA commented on YARN-1474: -- IIUC, javadoc warning is not related to the

[jira] [Created] (YARN-2114) Inform container of container-specific local directories

Jason Lowe created YARN-2114: Summary: Inform container of container-specific local directories Key: YARN-2114 URL: https://issues.apache.org/jira/browse/YARN-2114 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012519#comment-14012519 ] Tsuyoshi OZAWA commented on YARN-1474: -- Need to rebase on YARN-596. Please wait a

[jira] [Commented] (YARN-2114) Inform container of container-specific local directories

[ https://issues.apache.org/jira/browse/YARN-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012544#comment-14012544 ] Jason Lowe commented on YARN-2114: -- Currently a container can obtain a list of local

[jira] [Updated] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1474: - Attachment: YARN-1474.19.patch Rebased on trunk. Make schedulers services

[jira] [Commented] (YARN-2103) Inconsistency between viaProto flag and initial value of SerializedExceptionProto.Builder

[ https://issues.apache.org/jira/browse/YARN-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012572#comment-14012572 ] Junping Du commented on YARN-2103: -- Thanks [~decster] for the patch and [~ozawa] for

[jira] [Commented] (YARN-1474) Make schedulers services

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

[jira] [Commented] (YARN-2054) Poor defaults for YARN ZK configs for retries and retry-inteval

[ https://issues.apache.org/jira/browse/YARN-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012674#comment-14012674 ] Sandy Ryza commented on YARN-2054: -- +1 Poor defaults for YARN ZK configs for retries and

[jira] [Updated] (YARN-2054) Better defaults for YARN ZK configs for retries and retry-inteval when HA is enabled

[ https://issues.apache.org/jira/browse/YARN-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2054: --- Summary: Better defaults for YARN ZK configs for retries and retry-inteval when HA is enabled

[jira] [Updated] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2091: - Attachment: YARN-2091.2.patch Fixed to pass test. Add ContainerExitStatus.KILL_EXCEEDED_MEMORY

[jira] [Commented] (YARN-2054) Better defaults for YARN ZK configs for retries and retry-inteval when HA is enabled

[ https://issues.apache.org/jira/browse/YARN-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012710#comment-14012710 ] Tsuyoshi OZAWA commented on YARN-2054: -- +1(non-binding) Better defaults for YARN ZK

[jira] [Commented] (YARN-2112) Hadoop-client is missing jackson libs due to inappropriate configs in pom.xml

[ https://issues.apache.org/jira/browse/YARN-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012731#comment-14012731 ] Vinod Kumar Vavilapalli commented on YARN-2112: --- Looks good. Checking this

[jira] [Commented] (YARN-1368) Common work to re-populate containers’ state into scheduler

[ https://issues.apache.org/jira/browse/YARN-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012750#comment-14012750 ] Vinod Kumar Vavilapalli commented on YARN-1368: --- Started looking at this. It

[jira] [Commented] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

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

[jira] [Commented] (YARN-2112) Hadoop-client is missing jackson libs due to inappropriate configs in pom.xml

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

[jira] [Commented] (YARN-1368) Common work to re-populate containers’ state into scheduler

[ https://issues.apache.org/jira/browse/YARN-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012795#comment-14012795 ] Vinod Kumar Vavilapalli commented on YARN-1368: --- bq. Unless I'm missing

[jira] [Updated] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-2091: -- Target Version/s: 2.5.0 Targetting for 2.5.0. Let me look at it.. Add

[jira] [Commented] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012980#comment-14012980 ] Bikas Saha commented on YARN-2091: -- Instead of having the following if-else code

[jira] [Commented] (YARN-1368) Common work to re-populate containers’ state into scheduler

[ https://issues.apache.org/jira/browse/YARN-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013013#comment-14013013 ] Sandy Ryza commented on YARN-1368: -- Regardless of the technical approach taken in any

[jira] [Commented] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013052#comment-14013052 ] Vinod Kumar Vavilapalli commented on YARN-2091: --- Should we differentiate

[jira] [Commented] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013071#comment-14013071 ] Bikas Saha commented on YARN-2091: -- That would make sense if YARN would allow specifying

[jira] [Commented] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013093#comment-14013093 ] Tsuyoshi OZAWA commented on YARN-2091: -- Thanks for the suggestions, Bikas and Vinod.

[jira] [Commented] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013102#comment-14013102 ] Tsuyoshi OZAWA commented on YARN-2091: -- Found that it's simple enough adding methods

[jira] [Created] (YARN-2115) Replace RegisterNodeManagerRequest#ContainerStatus with a new ContainerRecoveryReport

Jian He created YARN-2115: - Summary: Replace RegisterNodeManagerRequest#ContainerStatus with a new ContainerRecoveryReport Key: YARN-2115 URL: https://issues.apache.org/jira/browse/YARN-2115 Project: Hadoop

[jira] [Updated] (YARN-2115) Replace RegisterNodeManagerRequest#ContainerStatus with a new ContainerRecoveryReport

[ https://issues.apache.org/jira/browse/YARN-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2115: -- Issue Type: Improvement (was: Bug) Replace RegisterNodeManagerRequest#ContainerStatus with a new

[jira] [Commented] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013119#comment-14013119 ] Sandy Ryza commented on YARN-2091: -- ContainerExitStatus should stay an int. While

[jira] [Updated] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2091: - Attachment: YARN-2091.3.patch Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app

[jira] [Updated] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

[ https://issues.apache.org/jira/browse/YARN-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-1913: -- Labels: (was: easyfix) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

[jira] [Updated] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

[ https://issues.apache.org/jira/browse/YARN-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-1913: -- Attachment: YARN-1913.patch Thanks, Sandy. Upload a new patch using the accurate way. With Fair Scheduler,

[jira] [Updated] (YARN-1877) ZK store: Add yarn.resourcemanager.zk-state-store.root-node.auth for root node auth

[ https://issues.apache.org/jira/browse/YARN-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-1877: Attachment: YARN-1877.patch ZK store: Add yarn.resourcemanager.zk-state-store.root-node.auth for

[jira] [Commented] (YARN-1877) ZK store: Add yarn.resourcemanager.zk-state-store.root-node.auth for root node auth

[ https://issues.apache.org/jira/browse/YARN-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013148#comment-14013148 ] Robert Kanter commented on YARN-1877: - Discussed with Karthik offline. There's no need

[jira] [Commented] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

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

[jira] [Commented] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

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

[jira] [Commented] (YARN-1877) ZK store: Add yarn.resourcemanager.zk-state-store.root-node.auth for root node auth

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

[jira] [Updated] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2091: - Attachment: YARN-2091.4.patch Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013201#comment-14013201 ] Vinod Kumar Vavilapalli commented on YARN-2010: --- bq. For completed

[jira] [Commented] (YARN-1366) ApplicationMasterService should Resync with the AM upon allocate call after restart

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013206#comment-14013206 ] Vinod Kumar Vavilapalli commented on YARN-1366: --- bq. Can we please

[jira] [Commented] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013207#comment-14013207 ] Vinod Kumar Vavilapalli commented on YARN-1365: --- bq. Can we please

[jira] [Updated] (YARN-2115) Replace RegisterNodeManagerRequest#ContainerStatus with a new ContainerRecoveryReport

[ https://issues.apache.org/jira/browse/YARN-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2115: -- Attachment: YARN-2115.1.patch Patch to replace the ContainerStatus with ContainerRecoveryReport Replace

[jira] [Commented] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

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

[jira] [Updated] (YARN-1709) Admission Control: Reservation subsystem

[ https://issues.apache.org/jira/browse/YARN-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subramaniam Krishnan updated YARN-1709: --- Attachment: YARN-1709.patch The attached patch contains in-memory data structures to

[jira] [Commented] (YARN-2115) Replace RegisterNodeManagerRequest#ContainerStatus with a new ContainerRecoveryReport

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

[jira] [Commented] (YARN-1366) ApplicationMasterService should Resync with the AM upon allocate call after restart

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013256#comment-14013256 ] Rohith commented on YARN-1366: -- Hi [~vinodkv], I agree that both issues title looks

[jira] [Updated] (YARN-1366) AM should implement Resync with the ApplicationMaster instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1366: Summary: AM should implement Resync with the ApplicationMaster instead of shutting down (was:

[jira] [Commented] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013281#comment-14013281 ] Anubhav Dhoot commented on YARN-1366: - Updated the title to more accurately reflect the

[jira] [Updated] (YARN-1366) AM should implement Resync with the ApplicationMasterService instead of shutting down

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1366: Summary: AM should implement Resync with the ApplicationMasterService instead of shutting down

[jira] [Updated] (YARN-2103) Inconsistency between viaProto flag and initial value of SerializedExceptionProto.Builder

[ https://issues.apache.org/jira/browse/YARN-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Binglin Chang updated YARN-2103: Attachment: YARN-2103.v1.patch Thanks for the review [~djp], update patch addressing your comments.

[jira] [Updated] (YARN-2103) Inconsistency between viaProto flag and initial value of SerializedExceptionProto.Builder

[ https://issues.apache.org/jira/browse/YARN-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Binglin Chang updated YARN-2103: Attachment: (was: YARN-2103.v1.patch) Inconsistency between viaProto flag and initial value of

[jira] [Updated] (YARN-2103) Inconsistency between viaProto flag and initial value of SerializedExceptionProto.Builder

[ https://issues.apache.org/jira/browse/YARN-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Binglin Chang updated YARN-2103: Attachment: YARN-2103.v2.patch updated wrong patch... resubmit Inconsistency between viaProto

[jira] [Commented] (YARN-2103) Inconsistency between viaProto flag and initial value of SerializedExceptionProto.Builder

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