stackabletech / stackabletech/hdfs-operator
Automatic bootstrapping of new JournalNodes
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 53
- Forks
- 9
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 10
Description
Adding new JournalNodes to HDFS can cause lead to problems. If for example a user starts with one node and then add two more for resilience the cluster won't start since only one node out of three has a valid journal. If a new journal node is added to a cluster it should bootstrap from an existing one to avoid this situation.
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
No file or test is named. Start by locating the HDFS JournalNode handling in the operator and determine how a newly added node can bootstrap from an existing valid journal. Done means a cluster expanded from one to three JournalNodes starts successfully with all journals valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100