hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinay (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5372) In FSNamesystem, hasReadLock() returns false if the current thread holds the write lock
Date Sun, 17 Nov 2013 16:19:22 GMT

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

Vinay updated HDFS-5372:
------------------------

    Affects Version/s: 3.0.0
                       2.2.0
               Status: Patch Available  (was: Open)

> 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: 2.2.0, 3.0.0
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Tsz Wo (Nicholas), SZE
>         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)

Mime
View raw message