Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sat, 21 Feb 2015 04:10:12 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12760288.1418077850000.101286.1424491812722@Atlassian.JIRA>
In-Reply-To: <JIRA.12760288.1418077850000@Atlassian.JIRA>
References: <JIRA.12760288.1418077850000@Atlassian.JIRA>
 <JIRA.12760288.1418077850275@arcas>
Subject: [jira] [Updated] (HDFS-7495) Lock inversion in
 DFSInputStream#getBlockAt()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ted Yu updated HDFS-7495:
-------------------------
    Resolution: Later
        Status: Resolved  (was: Patch Available)

> Lock inversion in DFSInputStream#getBlockAt()
> ---------------------------------------------
>
>                 Key: HDFS-7495
>                 URL: https://issues.apache.org/jira/browse/HDFS-7495
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Priority: Minor
>         Attachments: hdfs-7495-001.patch
>
>
> There're two locks: one on DFSInputStream.this , one on DFSInputStream.infoLock
> Normally lock is obtained on infoLock, then on DFSInputStream.infoLock
> However, such order is not observed in DFSInputStream#getBlockAt() :
> {code}
>     synchronized(infoLock) {
> ...
>       if (updatePosition) {
>         // synchronized not strictly needed, since we only get here
>         // from synchronized caller methods
>         synchronized(this) {
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)