TraceMachina / TraceMachina/nativelink
Create GrpcScheduler tests
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 244
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 54
Description
There are cases where proxying a Scheduler to another instance would be useful.
An example use case is where an instance sits close to clients that is running a fast-slow store for CAS and AC over a slow network connection. This would allow an action cache lookup scheduler to utilise the local AC and then forward actions that are not found to a remote scheduler that is closer to the workers.
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 locating GrpcScheduler and the existing scheduler tests. Determine how a scheduler proxy should use a local action cache and forward misses to a remote scheduler, then add tests covering that behavior and verify the test suite passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, rust
- Domain
- backend-api-design, distributed-systems, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100