hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9467) Fix data race accessing writeLockHeldTimeStamp in FSNamesystem
Date Thu, 26 Nov 2015 01:43:11 GMT

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

Hudson commented on HDFS-9467:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #725 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/725/])
HDFS-9467. Fix data race accessing writeLockHeldTimeStamp in (jing9: rev e556c35b0596700f9ec9d0a51cf5027259d531b5)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java


> Fix data race accessing writeLockHeldTimeStamp in FSNamesystem
> --------------------------------------------------------------
>
>                 Key: HDFS-9467
>                 URL: https://issues.apache.org/jira/browse/HDFS-9467
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.8.0
>            Reporter: Mingliang Liu
>            Assignee: Mingliang Liu
>             Fix For: 2.8.0
>
>         Attachments: HDFS-9467.000.patch, HDFS-9467.001.patch
>
>
> This is a followup of [HDFS-9145].
> Actually the value of {{writeLockInterval}} should be captured within the lock. The current
code has a race on {{writeLockHeldTimeStamp}}. Thanks to [~jingzhao] for reporting this.



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

Mime
View raw message