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-8164) cTime is 0 in VERSION file for newly formatted NameNode.
Date Thu, 08 Oct 2015 12:21:27 GMT

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

Hudson commented on HDFS-8164:
------------------------------

FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #471 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/471/])
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/FSNamesystem.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NNStorage.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSImage.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
>             Fix For: 2.8.0
>
>         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)

Mime
View raw message