Use NetworkClient in ambry-replication
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
Replication in ambry still uses blocking channels and `BlockingChannelConnectionPool`. This is the last user of blocking channels. ambry-replication needs to start using the `NetworkClient` so that
1. To stop using blocking channels and blocking paradigm
2. To abstract away network details from replication.
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 in the ambry-replication module by locating its uses of BlockingChannelConnectionPool and blocking channels, then read the NetworkClient API and its existing callers. Done means replication no longer uses blocking channels or the blocking paradigm and network details are abstracted behind NetworkClient.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100