[
https://issues.apache.org/jira/browse/YARN-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479673#comment-16479673
]
Eric Yang commented on YARN-8315:
-
[~hlhu...@us.ibm.com] Apache Hadoop community is not responsible for HDP
issues. However, I would suggest to look at the following configuration for
yarn-site.xml:
{code}
yarn.scheduler.capacity.schedule-asynchronously.enable
true
{code}
In addition to that, the 2.9.0/3.0.0 Yarn support specify multiple thread (by
default is 1) to allocate containers.
{code}
yarn.scheduler.capacity.schedule-asynchronously.maximum-threads
4
{code}
If the threads to schedule container is set to 1 or not enabled, it may cause
delay on container scheduling.
> HDP 3.0.0 perfromance is slower than HDP 2.6.4
> --
>
> Key: YARN-8315
> URL: https://issues.apache.org/jira/browse/YARN-8315
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn
>Affects Versions: 3.0.0
> Environment: I have a HDP 2.6.4 cluster and HDP 3.0.0 cluster, I set
> up to have the same settings for these two cluster such as java heap size,
> container size etc. They are both 4 node cluster with 3 data nodes. I took
> almost all the default setting on HDP 3.0.0 except that I modify the minimum
> container size to 64MB instead of 1024MB in both cluster.
>
>Reporter: Hsin-Liang Huang
>Priority: Major
>
> Hi, I am comparing the performance between HDP 3.0.0 and HDP 2.6.4 and I
> discovered HDP 3.0.0 is much slower than HDP 2.6.4 if the job acquire more
> yarn containers and we also pin point the problem is after the job is done,
> when it tried to clean up all the containers to exit the application, that's
> the place where it consumed more time than HDP 2.6.4. I used the simple
> yarn app that Hortonworks put out on github
> [https://github.com/hortonworks/simple-yarn-app] to do the testing. Below is
> my testing result from acquiring 8 containers in both HDP 3.0.0 and HDP 2.6.4
> cluster environment.
> =
> HDP 3.0.0:
> command: time hadoop jar
> /usr/hdp/3.0.0.0-829/hadoop-yarn/hadoop-yarn-applications-unmanaged-am-launcher-3.0.0.3.0.0.0-829.jar
> Client -classpath simple-yarn-app-1.1.0.jar -cmd "java
> com.hortonworks.simpleyarnapp.ApplicationMaster /bin/date 8"
> 18/05/17 11:06:42 INFO unmanagedamlauncher.UnmanagedAMLauncher: Initializing
> Client
> 18/05/17 11:06:42 INFO unmanagedamlauncher.UnmanagedAMLauncher: Starting
> Client
> 18/05/17 11:06:43 INFO client.RMProxy: Connecting to ResourceManager at
> whiny1.fyre.ibm.com/172.16.165.211:8050
> 18/05/17 11:06:43 INFO client.AHSProxy: Connecting to Application History
> server at whiny2.fyre.ibm.com/172.16.200.160:10200
> 18/05/17 11:06:43 INFO unmanagedamlauncher.UnmanagedAMLauncher: Setting up
> application submission context for ASM
> 18/05/17 11:06:43 INFO unmanagedamlauncher.UnmanagedAMLauncher: Setting
> unmanaged AM
> 18/05/17 11:06:43 INFO unmanagedamlauncher.UnmanagedAMLauncher: Submitting
> application to ASM
> 18/05/17 11:06:43 INFO impl.YarnClientImpl: Submitted application
> application_1526572577866_0011
> 18/05/17 11:06:44 INFO unmanagedamlauncher.UnmanagedAMLauncher: Got
> application report from ASM for, appId=11,
> appAttemptId=appattempt_1526572577866_0011_01, clientToAMToken=null,
> appDiagnostics=AM container is launched, waiting for AM container to Register
> with RM, appMasterHost=N/A, appQueue=default, appMasterRpcPort=-1,
> appStartTime=1526584003704, yarnAppState=ACCEPTED,
> distributedFinalState=UNDEFINED, appTrackingUrl=N/A, appUser=hlhuang
> 18/05/17 11:06:44 INFO unmanagedamlauncher.UnmanagedAMLauncher: Launching AM
> with application attempt id appattempt_1526572577866_0011_01
> 18/05/17 11:06:46 INFO client.RMProxy: Connecting to ResourceManager at
> whiny1.fyre.ibm.com/172.16.165.211:8030
> registerApplicationMaster 0
> registerApplicationMaster 1
> 18/05/17 11:06:47 INFO conf.Configuration: found resource resource-types.xml
> at file:/etc/hadoop/3.0.0.0-829/0/resource-types.xml
> Making res-req 0
> Making res-req 1
> Making res-req 2
> Making res-req 3
> Making res-req 4
> Making res-req 5
> Making res-req 6
> Making res-req 7
> Launching container container_e08_1526572577866_0011_01_01
> Launching container container_e08_1526572577866_0011_01_02
> Launching container container_e08_1526572577866_0011_01_03
> Launching container container_e08_1526572577866_0011_01_04
> Launching container container_e08_1526572577866_0011_01_05
> Launching container container_e08_1526572577866_0011_01_06
> Launching container container_e08_1526572577866_0011_01_07
> Launching container container_e08_1526572577866_0011_01_08
> Completed container
