[
https://issues.apache.org/jira/browse/HDFS-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G updated HDFS-5372:
--------------------------------------
Resolution: Fixed
Fix Version/s: 2.2.1
2.3.0
3.0.0
Status: Resolved (was: Patch Available)
Committed this to trunk, branch-2 and 2.2. Thanks
> In FSNamesystem, hasReadLock() returns false if the current thread holds the
> write lock
> ---------------------------------------------------------------------------------------
>
> Key: HDFS-5372
> URL: https://issues.apache.org/jira/browse/HDFS-5372
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.0.0, 2.2.0
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Vinay
> Fix For: 3.0.0, 2.3.0, 2.2.1
>
> Attachments: HDFS-5372.patch
>
>
> This bug was discovered by [~vinayrpet] in [this
> comment|https://issues.apache.org/jira/browse/HDFS-5283?focusedCommentId=13796752&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13796752].
> In FSNamesystem, there are hasReadLock() and hasReadOrWriteLock(). However,
> when a thread holds the write lock, the read lock is not required for reading
> data. So hasReadLock() and hasReadOrWriteLock() actually are the same.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
