This repository has been archived by the owner on Sep 9, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update guide README and add additional autoscaler guide details.
- Loading branch information
Showing
2 changed files
with
3 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,3 @@ | ||
# Sherpa Guides | ||
|
||
Welcome to the Sherpa guides. The guides provide examples for common Sherpa workflows and actions for both users and operators of Nomad clusters running Sherpa. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,3 @@ | ||
# AutoScaler | ||
|
||
Sherpa can run using an internal autoscaler which uses Nomad job resource utilization stats to determine whether a group should be scaled or not. | ||
Sherpa can run using an internal autoscaler which uses Nomad job resource utilization stats to determine whether a group is eligible for scaling. The autoscaler will iterate stored policies, performing calculations to figure out each job group CPU and memory consummation. If consumption is above 80% or below 20%, Sherpa will request scaling of the job group as long as the scaling policies limits are not violated. |