Avoid duplicate info about Hostname and Port in ClusterMapConfig and NetworkConfig
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
The hostname and port are currently recorded in ClusterMapConfig and NetworkConfig. We are supposed to avoid the duplicate information in two places for safety concerns. Maybe we can remove the hostname and port from NetworkConfig in the future.
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
Start by reading the ClusterMapConfig and NetworkConfig definitions and tracing where their hostname and port values are consumed. Determine which configuration should remain authoritative and inspect the affected tests or usages; done means the duplicate information is no longer maintained in both places without breaking configuration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100