-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add scaleup step size feature #132
Changes from all commits
162054e
01b621d
b193983
14a6477
4a07c8e
172fb2e
a5577e3
43e5d1b
a065979
e78d4af
3aa0a50
7f9f2b7
9b33ac6
dd009a9
15972a1
8434469
09f507a
0d848d8
44fca5c
87783d8
e7f95ab
ae47fad
46809d5
a85f59e
c4ef133
b453448
19ad040
bb399c5
2117743
8adf381
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -108,6 +108,14 @@ type ScaleConfig struct { | |
// The cool down period between two consecutive scaledown operations. If this option is omitted, the value of the `--scale-down-interval` command line option is taken as the default value. | ||
ScaledownInterval *metav1.Duration `json:"scaledownInterval,omitempty"` | ||
|
||
// The maximum number of processing units which can be added in one scale-up operation. It can be a multiple of 100 for values < 1000, or a multiple of 1000 otherwise. | ||
// +kubebuilder:default=0 | ||
ScaleupStepSize int `json:"scaleupStepSize,omitempty"` | ||
|
||
// How often autoscaler is reevaluated for scale up. | ||
// The warm up period between two consecutive scaleup operations. If this option is omitted, the value of the `--scale-up-interval` command line option is taken as the default value. | ||
ScaleupInterval *metav1.Duration `json:"scaleupInterval,omitempty"` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same as ScaleupStepSize There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I fixed it to 10 seconds because default interval for scaleup was set to 10 seconds before introducing scaleup feature. |
||
|
||
// The CPU utilization which the autoscaling will try to achieve. Ref: [Spanner CPU utilization](https://cloud.google.com/spanner/docs/cpu-utilization#task-priority) | ||
TargetCPUUtilization TargetCPUUtilization `json:"targetCPUUtilization"` | ||
} | ||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For compatibility, could you please make the default value zero and allow unlimited scaling?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fixed it to zero and if scaleupStepSize = 0, I made no scale up size limitation.
https://github.com/mercari/spanner-autoscaler/pull/132/files#diff-1984e42ef0a0d5e7edf140b3ae6decf3fd6e1b9bd4ee351d4dcd8cf7213bb537R569-R577