Automatic bootstrapping of new JournalNodes

Open
#423 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
kubernetes, rust
Domain
distributed-systems

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.

Description

customer-request

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.

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.