hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fenghua Hu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-10804) Use finer-granularity lock for ReplicaMap
Date Mon, 29 Aug 2016 07:42:20 GMT

     [ https://issues.apache.org/jira/browse/HDFS-10804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Fenghua Hu updated HDFS-10804:
    Status: Open  (was: Patch Available)

> Use finer-granularity lock for ReplicaMap
> -----------------------------------------
>                 Key: HDFS-10804
>                 URL: https://issues.apache.org/jira/browse/HDFS-10804
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs
>    Affects Versions: 3.0.0-beta1
>            Reporter: Fenghua Hu
>            Assignee: Fenghua Hu
>            Priority: Minor
> In currently implementation, ReplicaMap takes an external object as lock for synchronization.
> In function FsDatasetImpl#FsDatasetImpl(), the object is for synchronization is "this",
i.e. FsDatasetImpl: 
> volumeMap = new ReplicaMap(this);
> and in private FsDatasetImpl#addVolume(), "this" object is used for synchronization as
> ReplicaMap tempVolumeMap = new ReplicaMap(this);
> I am not sure if we really need so big object FsDatasetImpl  for ReplicaMap's synchronization.
If it's not necessary, this could reduce lock contention on FsDatasetImpl object and improve
> Could you please give me some suggestions? Thanks a lot!
> Fenghua

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message