You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "BELUGA BEHR (JIRA)" <ji...@apache.org> on 2018/10/12 18:11:00 UTC

[jira] [Updated] (HDFS-13990) Synchronization Issue With HashResolver.java

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

BELUGA BEHR updated HDFS-13990:
-------------------------------
    Status: Patch Available  (was: Open)

> Synchronization Issue With HashResolver.java
> --------------------------------------------
>
>                 Key: HDFS-13990
>                 URL: https://issues.apache.org/jira/browse/HDFS-13990
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: federation
>    Affects Versions: 3.2.0
>            Reporter: BELUGA BEHR
>            Assignee: BELUGA BEHR
>            Priority: Minor
>         Attachments: HDFS-13990.1.patch
>
>
> {code:java|title=HashResolver.java}
>   private ConsistentHashRing getHashResolver(final Set<String> namespaces) {
>     int hash = namespaces.hashCode();
>     ConsistentHashRing resolver = this.hashResolverMap.get(hash);
>     if (resolver == null) {
>       resolver = new ConsistentHashRing(namespaces);
>       this.hashResolverMap.put(hash, resolver);
>     }
>     return resolver;
>   }
> {code}
> The {{hashResolverMap}} is a {{ConcurrentHashMap}} so presumably there is concern here for concurrency issues.  However, there is no synchronization around this method, so two threads could call {{get(hash)}} both see a 'null' value and then both add two entries into the {{Map}}.  Add synchronization here.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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