[ https://issues.apache.org/jira/browse/MAPREDUCE-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095265#comment-15095265 ]
Hudson commented on MAPREDUCE-6473: ----------------------------------- FAILURE: Integrated in Hadoop-trunk-Commit #9098 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/9098/]) MAPREDUCE-6473. Job submission can take a long time during Cluster (jlowe: rev f657b54281d517c69df0a23b97b47befa77d1dc2) * hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/Cluster.java * hadoop-mapreduce-project/CHANGES.txt > Job submission can take a long time during Cluster initialization > ----------------------------------------------------------------- > > Key: MAPREDUCE-6473 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6473 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: performance > Reporter: Kuhu Shukla > Assignee: Kuhu Shukla > Fix For: 2.8.0 > > Attachments: 99%ile.png, MAPREDUCE-6473-PerfTest.txt, > MAPREDUCE-6473-v1.patch, MAPREDUCE-6473-v2.patch, MAPREDUCE-6473-v3.patch, > MAPREDUCE-6473-v4.patch, MAPREDUCE-6473-v5.patch, MAPREDUCE-6473-v6.patch, > MAPREDUCE-6473-v7.patch, avgtime.png > > > During initialization in Cluster.java, the framework provider classes are > loaded inside a sync block which can considerably increase job submission > time when the number of submissions are high. The motive is to reduce time > spent in this sync block safely to improve performance. > {noformat} > synchronized (frameworkLoader) { > for (ClientProtocolProvider provider : frameworkLoader) { > LOG.debug("Trying ClientProtocolProvider : " > + provider.getClass().getName()); > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)