[
https://issues.apache.org/jira/browse/HDFS-8269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521705#comment-14521705
]
Hudson commented on HDFS-8269:
------------------------------
SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2129 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2129/])
HDFS-8269. getBlockLocations() does not resolve the .reserved path and
generates incorrect edit logs when updating the atime. Contributed by Haohui
Mai. (wheat9: rev 3dd6395bb2448e5b178a51c864e3c9a3d12e8bc9)
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestGetBlockLocations.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NamenodeFsck.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFsck.java
> getBlockLocations() does not resolve the .reserved path and generates
> incorrect edit logs when updating the atime
> -----------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-8269
> URL: https://issues.apache.org/jira/browse/HDFS-8269
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Yesha Vora
> Assignee: Haohui Mai
> Priority: Blocker
> Fix For: 2.7.1
>
> Attachments: HDFS-8269.000.patch, HDFS-8269.001.patch,
> HDFS-8269.002.patch, HDFS-8269.003.patch
>
>
> When {{FSNamesystem#getBlockLocations}} updates the access time of the INode,
> it uses the path passed from the client, which generates incorrect edit logs
> entries:
> {noformat}
> <RECORD>
> <OPCODE>OP_TIMES</OPCODE>
> <DATA>
> <TXID>5085</TXID>
> <LENGTH>0</LENGTH>
> <PATH>/.reserved/.inodes/18230</PATH>
> <MTIME>-1</MTIME>
> <ATIME>1429908236392</ATIME>
> </DATA>
> </RECORD>
> {noformat}
> Note that the NN does not resolve the {{/.reserved}} path when processing the
> edit log, therefore it eventually leads to a NPE when loading the edit logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
