Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 5 Oct 2015 22:57:28 +0000 (UTC)
From: "Xiao Chen (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12821641.1429211818000.31233.1444085848599@Atlassian.JIRA>
In-Reply-To: <JIRA.12821641.1429211818000@Atlassian.JIRA>
References: <JIRA.12821641.1429211818000@Atlassian.JIRA>
 <JIRA.12821641.1429211818555@arcas>
Subject: [jira] [Updated] (HDFS-8164) cTime is 0 in VERSION file for newly
 formatted NameNode.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Xiao Chen updated HDFS-8164:
----------------------------
    Status: Open  (was: Patch Available)

> 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)