[
https://issues.apache.org/jira/browse/HDFS-15287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akira Ajisaka updated HDFS-15287:
---------------------------------
Target Version/s: 3.4.0 (was: 3.3.0, 2.10.1)
Priority: Major (was: Blocker)
Hi [~kihwal], would you check whether the patch in HDFS-15293 fixes the
side-effect or not?
I lowered the priority and set release-blocker label to the follow-up jira
(HDFS-15293).
> HDFS rollingupgrade prepare never finishes
> ------------------------------------------
>
> Key: HDFS-15287
> URL: https://issues.apache.org/jira/browse/HDFS-15287
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.10.0, 3.3.0
> Reporter: Kihwal Lee
> Priority: Major
>
> After HDFS-12979, the prepare step of rolling upgrade does not work. This is
> because it added additional check for sufficient time passing since last
> checkpoint. Since RU rollback image creation and upload can happen any time,
> uploading of rollback image never succeeds. For a new cluster deployed for
> testing, it might work since it never checkpointed before.
> It was found that this check is disabled for unit tests, defeating the very
> purpose of testing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
