TraceMachina / TraceMachina/nativelink
Worker connection failures on startup shouldn't raise errors
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 244
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 54
Description
At the moment we raise errors when the worker can't find the scheduler:
https://github.com/TraceMachina/nativelink/actions/runs/7558646440/job/20580653217?pr=614#step:9:197
This might lead to issues when running health and readiness checks and readiness checks in K8s. We should find a solution that integrates better with the K8s scheduler.
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 with the linked GitHub Actions job and trace the worker startup path where it cannot find the scheduler. Review how health and readiness checks behave in this situation, then define completion as avoiding inappropriate startup errors while integrating readiness behavior with the Kubernetes scheduler.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- cloud, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100