hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-8164) cTime is 0 in VERSION file for newly formatted NameNode.
Date Thu, 16 Apr 2015 19:17:59 GMT

     [ https://issues.apache.org/jira/browse/HDFS-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Nauroth updated HDFS-8164:
--------------------------------
    Description: 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.  (was: 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 a value
of 0 can cause confusion.)

> 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
>            Priority: Minor
>
> 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