Secondary NameNode bootstrap gets stuck on HDFS 3.3.6

Open
#440 3 comments 1 reaction 1 assignee View on GitHub

@lfrancke is already working on this.

Since Mar 6, 2024.

Assessment

This issue has not been assessed yet.

Description

type/bug
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

Dominant language
Rust
Stars
53
Forks
9
Avg merge
1d 13h
Merged PRs (30d)
10

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/hdfs-operator

All issues in stackabletech/hdfs-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.