Data Channel flow control -- GRPC max data buffer upper limit
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 29
- Forks
- 30
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 6
Description
Problem Statement:
-
Push data channel, we need to do grpc max data upper limit control, which is similar to what Fetch data channel has done (e.g. config value to do the staged data push).
-
Another case is, one blob put is doing write to 32MB for example, and it can be addressed in one remote_blkid.
Currently we can only do flow control per rreq entry which maps to one remote_blkid. However if this remote_blkid addresses more than grpc max data buffer limit (which currently believed to be around a few MBs, needs to be tested before we move ahead), we need to handle this case.
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
No files, tests, or entry points are named. Start by measuring the current gRPC maximum data buffer and comparing Push data channel behavior with the existing Fetch data channel flow control. Done means defining and implementing staged data push plus flow control for a single blob that exceeds the gRPC buffer limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100