stackabletech / stackabletech/hdfs-operator
DataNode cannot register with NameNode
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 53
- Forks
- 9
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 10
Description
We've seen one instance where a DataNode is not allowed to register with the NameNode.
We see this error in the logs:
Datanode denied communication with namenode because hostname cannot be resolved
And the NameNode logs:
Unresolved datanode registration
Setting dfs.namenode.datanode.registration.ip-hostname-check to false might help but we're not sure.
We have not been able to find the source for this issue yet.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the operator and its tests for the log messages “Datanode denied communication with namenode because hostname cannot be resolved” and “Unresolved datanode registration.” Then trace how the operator configures DataNode and NameNode registration, including dfs.namenode.datanode.registration.ip-hostname-check. Done means identifying the cause and verifying a registration fix or documenting why the setting is relevant.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100