[ https://issues.apache.org/jira/browse/HDFS-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948156#comment-14948156 ]
Hudson commented on HDFS-8164: ------------------------------ FAILURE: Integrated in Hadoop-trunk-Commit #8593 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/8593/]) HDFS-8164. cTime is 0 in VERSION file for newly formatted NameNode. (yzhang: rev 1107bd399c790467b22e55291c2611fd1c16e156) * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NNStorage.java * hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSImage.java * hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java > cTime is 0 in VERSION file for newly formatted NameNode. > -------------------------------------------------------- > > Key: HDFS-8164 > URL: https://issues.apache.org/jira/browse/HDFS-8164 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode > Affects Versions: 2.0.3-alpha > Reporter: Chris Nauroth > Assignee: Xiao Chen > Priority: Minor > Attachments: HDFS-8164.001.patch, HDFS-8164.002.patch, > HDFS-8164.003.patch, HDFS-8164.004.patch, HDFS-8164.005.patch, > HDFS-8164.006.patch, HDFS-8164.007.patch > > > After formatting a NameNode and inspecting its VERSION file, the cTime > property shows 0. The value does get updated to current time during an > upgrade, but I believe this is intended to be the creation time of the > cluster, and therefore the initial value of 0 before an upgrade can cause > confusion. -- This message was sent by Atlassian JIRA (v6.3.4#6332)