[
https://issues.apache.org/jira/browse/HDFS-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14081778#comment-14081778
]
Hadoop QA commented on HDFS-6797:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12658983/HDFS-6797.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/7516//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7516//console
This message is automatically generated.
> Misleading LayoutVersion information during data node 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
> 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)
