Details
Description
With HA enabled, NN wo't start with "-upgrade". Since there has been a layout version change between 2.0.x and 2.1.x, starting NN in upgrade mode was necessary when deploying 2.1.x to an existing 2.0.x cluster. But the only way to get around this was to disable HA and upgrade.
The NN and the cluster cannot be flipped back to HA until the upgrade is finalized. If HA is disabled only on NN for layout upgrade and HA is turned back on without involving DNs, things will work, but finaliizeUpgrade won't work (the NN is in HA and it cannot be in upgrade mode) and DN's upgrade snapshots won't get removed.
We will need a different ways of doing layout upgrade and upgrade snapshot. I am marking this as a 2.1.1-beta blocker based on feedback from others. If there is a reasonable workaround that does not increase maintenance window greatly, we can lower its priority from blocker to critical.
Attachments
Attachments
Issue Links
- breaks
-
HDFS-8127 NameNode Failover during HA upgrade can cause DataNode to finalize upgrade
- Closed
-
HDFS-8469 Lockfiles are not being created for datanode storage directories
- Patch Available
- duplicates
-
HDFS-3958 Integrate upgrade/finalize/rollback with external journals
- Resolved
-
HDFS-3133 Add support for DFS upgrade with HA enabled
- Resolved
- is related to
-
HDFS-2952 HA: NN should not start with upgrade option or with a pending an unfinalized upgrade
- Resolved
-
HDFS-3225 Revist upgrade snapshots, roll back, finalize to enable rolling upgrades
- Resolved
-
HDFS-8241 Remove unused NameNode startup option -finalize
- Resolved
- relates to
-
HDFS-5223 Allow edit log/fsimage format changes without changing layout version
- Open
- requires
-
HDFS-5840 Follow-up to HDFS-5138 to improve error handling during partial upgrade failures
- Closed