Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <813275035.1213907505094.JavaMail.jira@brutus>
Date: Thu, 19 Jun 2008 13:31:45 -0700 (PDT)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3487) Balancer should not allocate a
 thread per block move
In-Reply-To: <409028288.1212537045092.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606547#action_12606547 ] 

Tsz Wo (Nicholas), SZE commented on HADOOP-3487:
------------------------------------------------

- It is better to use ExecutorService.submit(...) than Executor.execute(...).  A Future object will be returned by submit(...) and it can be used for waiting the task termination.  Then, dispatcherCount is not needed.

- The InterruptedException in dispatchBlockMoves() should not be ignored.  We need to shutdown the ExecutorService and terminate the program.

> Balancer should not allocate a thread per block move
> ----------------------------------------------------
>
>                 Key: HADOOP-3487
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3487
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.17.0
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>            Priority: Blocker
>             Fix For: 0.18.0
>
>         Attachments: balancerThread.patch
>
>
> It will be more efficient to use a thread pool to provision thread for each block move.

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