redpanda-data / redpanda-data/redpanda
Add a way to tweak configuration in the log
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.6k
- Forks
- 792
- PR merge metrics
- No merged PRs in 30d
Description
Who is this for and what problem do they have today?
One example this came up with was two replicas were accidentally assigned to a single broker. There were two things:
- Redpanda didn't refuse such disruptive operation --> addressed by https://github.com/redpanda-data/redpanda/pull/3846 and shipped with v21.11.8
- Redpanda didn't have a way to change replica assignment configuration in the log
What are the success criteria?
For the latter in the above, let's make a tool available to change the configuration in the log in a fairly easy way to save the cluster from the disruptive scenario
Why is solving this problem impactful?
This improves operability and supportability of Redpanda
JIRA Link: CORE-853
Contributor guide
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
The issue does not name any files, tests, or entry points. Start by reviewing the existing replica-assignment and log-configuration paths, then define the tool's supported operation and recovery behavior for a disruptive cluster state. Done means operators can safely change replica assignment configuration in the log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100