[ https://issues.apache.org/jira/browse/HDFS-9208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14964479#comment-14964479 ]
Hudson commented on HDFS-9208: ------------------------------ FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #571 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/571/]) HDFS-9208. Disabling atime may fail clients like distCp. (Kihwal Lee via (yliu: rev 9cb5d353533e829e624b33fb26dd37c177e1e046) * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirAttrOp.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestSetTimes.java > Disabling atime may fail clients like distCp > -------------------------------------------- > > Key: HDFS-9208 > URL: https://issues.apache.org/jira/browse/HDFS-9208 > Project: Hadoop HDFS > Issue Type: Bug > Reporter: Kihwal Lee > Assignee: Kihwal Lee > Fix For: 2.8.0 > > Attachments: HDFS-9208.patch, HDFS-9208.v2.patch > > > When atime is disabled, {{setTimes()}} throws an exception if the passed-in > atime is not -1. But since atime is not -1, distCp fails when it tries to > set the mtime and atime. > There are several options: > 1) make distCp check for 0 atime and call {{setTimes()}} with -1. I am not > very enthusiastic about it. > 2) make NN also accept 0 atime in addition to -1, when the atime support is > disabled. > 3) support setting mtime & atime regardless of the atime support. The main > reason why atime is disabled is to avoid edit logging/syncing during > {{getBlockLocations()}} read calls. Explicit setting can be allowed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)