Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Secondary NameNode bootstrap gets stuck on HDFS 3.3.6 #440

Open
nightkr opened this issue Dec 18, 2023 · 3 comments
Open

Secondary NameNode bootstrap gets stuck on HDFS 3.3.6 #440

nightkr opened this issue Dec 18, 2023 · 3 comments
Assignees
Labels

Comments

@nightkr
Copy link
Member

nightkr commented Dec 18, 2023

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

@nightkr
Copy link
Member Author

nightkr commented Mar 7, 2024

Another maybe-related symptom of this:

After starting an old cluster back up neither namenode was able to become Active. They'd wait for their blocks and try to transition into active, but would get stuck halfway, eventually giving up and being restarted as standby, waiting for the cycle to repeat again.

@fhennig
Copy link
Contributor

fhennig commented May 27, 2024

@lfrancke this ticket hasn't moved since March 6, what is needed to move this along?

@lfrancke
Copy link
Member

I need to get to it at some point. This is mostly a reminder at this point to not forget about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants