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

Shilun Fan updated HDFS-16973:
------------------------------
          Component/s: rbf
     Target Version/s: 3.4.0
    Affects Version/s: 3.4.0

> RBF: MountTableResolver cache size lookup should take read lock
> ---------------------------------------------------------------
>
>                 Key: HDFS-16973
>                 URL: https://issues.apache.org/jira/browse/HDFS-16973
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: rbf
>    Affects Versions: 3.4.0
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>
> Mount table resolver location cache gets invalidated by taking write lock as 
> part of addEntry/removeEntry/refreshEntries calls. Since the write lock 
> exclusively updates the cache, getDestinationForPath already takes read lock 
> before accessing the cache. Similarly, retrieval of the cache size should 
> also take the read lock.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to