Update worker to be able to reference a local scheduler
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- rust
- Domain
- backend, build-system, distributed-systems
Research direction
Start by tracing how worker_api_endpoint.uri is parsed and how scheduler names are resolved. Define the behavior for a local:// URI, including how a worker finds the named local scheduler without exposing a gRPC port. Done means local scheduler references work for workers while existing URI schemes continue to work; add or update tests for both paths.
Written by the indexing model from the issue text.
Description
If using a Redis scheduler, there's very little need to have a connection between the worker and the scheduler pool. Instead, each worker can simply run its own internal scheduler which assigns work to its own workers. This is also useful for testing on a local machine rather than requiring a loopback address.
Although this is already supported by simply using a loopback, it would be nice if it was supported internally without having to expose the gRPC port.
The proposal is to update the worker_api_endpoint.uri to support a scheme "local://" which references the local scheduler by name.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 244
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 54
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.
More from TraceMachina/nativelink
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
TraceMachina/nativelink#2779 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TraceMachina/nativelink#2770 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
TraceMachina/nativelink#2672 · 2 comments ·
-
TraceMachina/nativelink#2649 · 3 comments · 2 assignees ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
TraceMachina/nativelink#2609 ·
All issues in TraceMachina/nativelink
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100