[
https://issues.apache.org/jira/browse/HDFS-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942864#comment-14942864
]
Xiao Chen commented on HDFS-8164:
---------------------------------
Thanks Yongjun again for the review and comments.
I have addressed comment #1 to add comments. Please see if it makes sense to
you.
I also added the nullity check on {{FSNamesystem}} to check {{fsImage}}.
However, the {{NNStorage}} variable on {{FSImage}} cannot be null, since it's
created during initialization. Also, I think this is the reason why other
{{getStorage}} calls do not check nullity.
Thanks a lot!
> 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
>
>
> 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)
