Replace usage of BlockingChannel in tools to NetworkClient
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
Some of the tools uses BlockingChannel to interact with Servers. This needs to be replaced with NetworkClient.
AdminTool
BlobValidator
ServerTool
ServerReadPerformance
ServerWritePerformance
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
Locate the BlockingChannel usage in AdminTool, BlobValidator, ServerTool, ServerReadPerformance, and ServerWritePerformance, then read the existing NetworkClient usage nearby. Verify that each tool still interacts with servers correctly through NetworkClient; completion means no listed tool uses BlockingChannel.
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