Xiaoyu Yao created HDFS-11209:
---------------------------------
Summary: SNN can't checkpoint when rolling upgrade is not finalized
Key: HDFS-11209
URL: https://issues.apache.org/jira/browse/HDFS-11209
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
Similar problem has been fixed with HDFS-7185. Recent change in HDFS-8432
brings this back.
With HDFS-8432, the primary NN will not update the VERSION file to the new
version after running with "rollingUpgrade" option until upgrade is finalized.
This is to support more downgrade use cases.
However, the checkpoint on the SNN is incorrectly updating the VERSION file
when the rollingUpgrade is not finalized yet. As a result, the SNN checkpoint
successfully but fail to push it to the primary NN because its version is
higher than the primary NN as shown below.
{code}
2016-12-02 05:25:31,918 ERROR namenode.SecondaryNameNode
(SecondaryNameNode.java:doWork(399)) - Exception in doCheckpoint
org.apache.hadoop.hdfs.server.namenode.TransferFsImage$HttpPutFailedException:
Image uploading failed, status: 403, url:
http://NN:50070/imagetransfer?txid=345404754&imageFile=IMAGE&File-Le...,
message: This namenode has storage info -60:221856466:1444080250181:clusterX
but the secondary expected -63:221856466:1444080250181:clusterX
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
