redpanda-data / redpanda-data/redpanda
Don't force a broker restart when changing node configurations that don't require it.
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?
Currently, changing node configurations such as advertised_rpc_api and advertised_kafka_api for 1 listener requires the user to restart the broker for it to take effect, disconnecting all other clients connected to listeners that were not changed.
What are the success criteria?
Node configurations that don't technically require a broker restart can be updated without restarting a broker and/or disrupting clients.
Why is solving this problem impactful?
This helps users operating Redpanda at scale to update node configurations and operate the system without causing unnecessary service disruptions for their users.
JIRA Link: CORE-1323
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
Start by tracing how advertised_rpc_api and advertised_kafka_api changes are processed, including the broker restart and client-disconnection paths. Determine which node configuration updates can be applied in place; done means eligible changes avoid restarting the broker or disrupting clients on unchanged listeners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, kafka
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100