584eeefdc8
Moves the query_retry method into the baseclass and makes the query retry and timeout options part of the watcher_datasources config group. This makes the query_retry behavior uniform across all datasources. A new baseclass method named query_retry_reset is added so datasources can define operations to perform when recovering from a query error. Test cases are added to verify the behavior of query_retry. The query_max_retries and query_timeout config parameters are deprecated in the gnocchi_client group and will be removed in a future release. Change-Id: I33e9dc2d1f5ba8f83fcf1488ff583ca5be5529cc
17 lines
764 B
YAML
17 lines
764 B
YAML
---
|
|
features:
|
|
- |
|
|
All datasources can now be configured to retry retrieving a metric upon
|
|
encountering an error. Between each attempt will be a set amount of time
|
|
which can be adjusted from the configuration. These configuration
|
|
options can be found in the `[watcher_datasources]` group and are named
|
|
`query_max_retries` and `query_timeout`.
|
|
upgrade:
|
|
- |
|
|
If Gnocchi was configured to have a custom amount of retries and or a
|
|
custom timeout then the configuration needs to moved into the
|
|
`[watcher_datasources]` group instead of the `[gnocchi_client]` group.
|
|
deprecations:
|
|
- |
|
|
The configuration options for query retries in `[gnocchi_client]` are
|
|
deprecated and the option in `[watcher_datasources]` should now be used. |