hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4664) Parallelize job initialization
Date Mon, 09 Feb 2009 11:40:59 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671813#action_12671813

Tom White commented on HADOOP-4664:

Generally looks good. A few comments:

* Rather than managing threads explicitly, it might be easier to use ThreadPoolExecutor (http://java.sun.com/javase/6/docs/api/java/util/concurrent/ThreadPoolExecutor.html)
* Do you think you can write a test for EagerTaskInitializationListener?
* There are some tabs in the patch.

> Parallelize job initialization
> ------------------------------
>                 Key: HADOOP-4664
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4664
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Matei Zaharia
>            Assignee: Matei Zaharia
>         Attachments: parallel-job-init-v1.patch
> The job init thread currently initializes one job at a time. However, this is a lengthy
and partly IO-bound process because all of the job's block locations need to be resolved through
the namenode and a map of them needs to be built. It can take tens of seconds. As a result,
the cluster sometimes initializes jobs too slowly for full utilization to be achieved, if
there are many small jobs queued up. It would be better to have a pool of threads that initialize
multiple jobs in parallel. One thing to be careful of, however, is not causing deadlocks or
holding locks for too long in these threads.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message