[
https://issues.apache.org/jira/browse/HDFS-15287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee updated HDFS-15287:
------------------------------
Description:
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.
was:
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 purpose of
testing.
> 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: Blocker
>
> 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]
