Docker Swarm Scheduling Performance with node.id Constraint
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
If I created a service with docker swarm specifying e.g. node.id==node42 as a constraint what would happen from the point of view of the scheduling process? The process would be performed entirely taking into account the constraint or, having specified a constraint that forces the choice to a single node, docker only takes care of verifying if the choice is admissible "skipping" then the whole scheduling process?
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
No files, tests, or entry points are named. First identify the scheduler code that evaluates node.id constraints and determine how scheduling proceeds when only one node is admissible. Done means providing a confirmed explanation of the scheduling process and its performance implications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- distributed-systems
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100