[
https://issues.apache.org/jira/browse/HDFS-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Chen updated HDFS-8164:
----------------------------
Attachment: HDFS-8164.003.patch
Thanks [~yzhangal] for the review! Your comments make sense to me.
I have uploaded a new patch encapsulating {{FSNameSystem#getCTime}}. I leave
{{FSImage}} untouched for now, if in the future {{getCTime}} is needed from
there, it can be easily added.
> 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
>
>
> 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)
