Description
After a cluster is upgraded I see a mismatch in layoutVersion between NN VERSION file and JN VERSION file.
Here is what I see:
Before cluster upgrade:
==================
## Version file from NN current directory namespaceID=109645726 clusterID=CID-edcb62c5-bc1f-49f5-addb-37827340b5de cTime=0 storageType=NAME_NODE blockpoolID=BP-786201894-10.0.100.11-1466026941507 layoutVersion=-60
## Version file from JN current directory namespaceID=109645726 clusterID=CID-edcb62c5-bc1f-49f5-addb-37827340b5de cTime=0 storageType=JOURNAL_NODE layoutVersion=-60
After cluster upgrade:
=================
## Version file from NN current directory namespaceID=109645726 clusterID=CID-edcb62c5-bc1f-49f5-addb-37827340b5de cTime=0 storageType=NAME_NODE blockpoolID=BP-786201894-10.0.100.11-1466026941507 layoutVersion=-63
## Version file from JN current directory namespaceID=109645726 clusterID=CID-edcb62c5-bc1f-49f5-addb-37827340b5de cTime=0 storageType=JOURNAL_NODE layoutVersion=-60
Since Namenode is what creates Journalnode VERSION file during initializeSharedEdits, it should also update the file with correct information after the cluster is upgraded and hdfs dfsadmin -finalizeUpgrade has been executed.