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-6797) DataNode logs wrong layoutversion during upgrade
Date Fri, 01 Aug 2014 04:43:40 GMT

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

Hudson commented on HDFS-6797:
------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #5993 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5993/])
HDFS-6797. DataNode logs wrong layoutversion during upgrade. (Contributed by Benoy Antony)
(arp: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1615017)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BlockPoolSliceStorage.java


> DataNode logs wrong layoutversion during upgrade
> ------------------------------------------------
>
>                 Key: HDFS-6797
>                 URL: https://issues.apache.org/jira/browse/HDFS-6797
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>    Affects Versions: 2.4.1
>            Reporter: Benoy Antony
>            Assignee: Benoy Antony
>             Fix For: 3.0.0, 2.6.0
>
>         Attachments: HDFS-6797.patch
>
>
> Before upgrade, data node version was -55. The new data node version remained at -55.
During upgrade we got he following messages:
> {code}
> 2014-07-15 12:59:55,253 INFO org.apache.hadoop.hdfs.server.common.Storage: Data-node
version: -55 and name-node layout version: -56
> ...
> ...
> ...
> ...
> 2014-07-15 12:59:56,479 INFO org.apache.hadoop.hdfs.server.common.Storage: Upgrading
block pool storage directory /hadoop/1/data1/current/BP-825373266-xx.xxx.xxx.xx-1379095203239.
>    old LV = -55; old CTime = 1402508907789.
>    new LV = -56; new CTime = 1405453914270
> 2014-07-15 13:00:07,697 INFO org.apache.hadoop.hdfs.server.common.Storage: Upgrade of
block pool BP-825373266-xx.xxx.xxx.xx-1379095203239 at /hadoop/12/data1/current/BP-825373266-xx.xxx.xxx.xx-1379095203239
is complete
> 2014-07-15 13:00:07,839 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Setting
up storage: nsid=859725752;bpid=BP-825373266-xx.xxx.xxx.xx-1379095203239;lv=-55;nsInfo=lv=-56;cid=CID-303ee504-e03c-4a5e-bc59-2b275b308152;nsid=859725752;c=1405453914270;bpid=BP-82537326
> 6-xx.xxx.xxx.xx-1379095203239;dnuuid=b1011b87-d7cd-48ce-92cc-f7cca0e8cbae
> {code}
> after upgrade completing, restart of DN still shows message regarding version difference:
> {code}
> INFO org.apache.hadoop.hdfs.server.common.Storage: Data-node version: -55 and name-node
layout version: -56
> {code}
> This causes confusion to the operators as if upgrade did not succeed since data node's
layout version is not updated to the "new LV" value
> Actually name node's layout version is displayed as the "new LV" value.
> Since the data node and name node layout versions are separate now, the new data node
layout version should be shown as the “new LV”.  
> Thanks to [~ehf] who found and reported this issue.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message