Spike: Scale servers concurrently
@ess is already working on this.
Since Apr 8, 2019.
Assessment
This issue has not been assessed yet.
Description
While the "Individual" scaling strategy only ever acts on a single server, the "Legion" strategy acts on all applicable servers.
At present, this is an iterative process that turns those servers on/off one-by-one, which can take a significant amount of time.
To that end, we should consider running those start/stop processes concurrently and waiting for the operation group to finish.
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from engineyard/scaley
-
enhancement
engineyard/scaley#35 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
engineyard/scaley#32 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 25/100
engineyard/scaley#31 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
engineyard/scaley#30 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
engineyard/scaley#23 · 3 comments ·
All issues in engineyard/scaley
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100