Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <873351563.1218665444302.JavaMail.jira@brutus>
Date: Wed, 13 Aug 2008 15:10:44 -0700 (PDT)
From: "Raghu Angadi (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3943)
 NetworkTopology.pseudoSortByDistance does not need to be a synchronized
 method
In-Reply-To: <26083534.1218586064342.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-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622368#action_12622368 ] 

Raghu Angadi commented on HADOOP-3943:
--------------------------------------

I guess we missed converting this to use read lock as part of HADOOP-1269. Would that be the fix? 

> NetworkTopology.pseudoSortByDistance does not need to be a synchronized method
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-3943
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3943
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>             Fix For: 0.19.0
>
>
> When all requests to namenode are read, most handlers block on NetworkTopology object lock when sorting replicas. Removing this necessary lock would reduce the contention in namenode and therefore improve its throughput.

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