policy: add query_window_offset
configuration
#850
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Nomad Autoscaler uses the current time as the end of the query window. This can cause instability, specially for strategies that only take the most recent data point into account, because the latest data may still be processing.
query_window_offset
defines a time offset applied to the query window to push it back in time. A shortquery_window_offset
value can help with the unstable readings, and a long value can be used for predictive scaling based on historical data (for example, from7d
ago).Closes #843.