Open
Description
Affected version
23.11.0
Current and expected behavior
Typically, one namenode does an initial format, and then another tries to bootstrap from the first.
However, for some reason the secondary seems to get stuck bootstrapping in some clusters, never letting the cluster initialize fully.
3.3.4 does not seem to show the same issue.
Possible solution
No response
Additional context
No response
Environment
Client Version: v1.27.4
Kustomize Version: v5.0.1
Server Version: v1.27.3
Deployed using ctlptl 0.8.22, kind 0.20.0.
Would you like to work on fixing this bug?
None