[ 
https://issues.apache.org/jira/browse/HDFS-16973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709111#comment-17709111
 ] 

ASF GitHub Bot commented on HDFS-16973:
---------------------------------------

goiri merged PR #5533:
URL: https://github.com/apache/hadoop/pull/5533




> 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
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to