Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1B4B1104BB for ; Sun, 17 Nov 2013 18:47:23 +0000 (UTC) Received: (qmail 77746 invoked by uid 500); 17 Nov 2013 18:47:22 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 77714 invoked by uid 500); 17 Nov 2013 18:47:22 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 77705 invoked by uid 99); 17 Nov 2013 18:47:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Nov 2013 18:47:22 +0000 Date: Sun, 17 Nov 2013 18:47:22 +0000 (UTC) From: "Tsz Wo (Nicholas), SZE (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (HDFS-5372) In FSNamesystem, hasReadLock() returns false if the current thread holds the write lock MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE reassigned HDFS-5372: -------------------------------------------- Assignee: Vinay (was: Tsz Wo (Nicholas), SZE) No problem. I am glad that you pick this up. Assigning to you. > 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 > 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)