[
https://issues.apache.org/jira/browse/HDFS-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027665#comment-15027665
]
Jing Zhao commented on HDFS-9467:
---------------------------------
The patch looks good to me. One nit is that the "isInfoEnabled" check may be
unnecessary. Other than this +1.
> 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
> Attachments: HDFS-9467.000.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)