|
2 | 2 |
|
3 | 3 | ## master / unreleased
|
4 | 4 |
|
| 5 | +* [FEATURE] Fan out parallelizable queries to backend queriers concurrently. #1878 |
| 6 | + * `-querier.sum-shards` (bool) |
| 7 | + * Requires a shard-compatible schema (v10+) |
| 8 | + * This causes the number of traces to increase accordingly. |
| 9 | + * The query-frontend now requires a schema config to determine how/when to shard queries, either from a file or from flags (i.e. by the `config-yaml` CLI flag). This is the same schema config the queriers consume. The schema is only required to use this option. |
| 10 | + * It's also advised to increase downstream concurrency controls as well: |
| 11 | + * `querier.max-outstanding-requests-per-tenant` |
| 12 | + * `querier.max-query-parallelism` |
| 13 | + * `querier.max-concurrent` |
| 14 | + * `server.grpc-max-concurrent-streams` (for both query-frontends and queriers) |
5 | 15 | * [CHANGE] The frontend http server will now send 502 in case of deadline exceeded and 499 if the user requested cancellation. #2156
|
6 | 16 | * [CHANGE] Config file changed to remove top level `config_store` field in favor of a nested `configdb` field. #2125
|
7 | 17 | * [CHANGE] Removed unnecessary `frontend.cache-split-interval` in favor of `querier.split-queries-by-interval` both to reduce configuration complexity and guarantee alignment of these two configs. Starting from now, `-querier.cache-results` may only be enabled in conjunction with `-querier.split-queries-by-interval` (previously the cache interval default was `24h` so if you want to preserve the same behaviour you should set `-querier.split-queries-by-interval=24h`). #2040
|
@@ -62,17 +72,6 @@ Note that the ruler flags need to be changed in this upgrade. You're moving from
|
62 | 72 | Further, if you're using the configs service, we've upgraded the migration library and this requires some manual intervention. See full instructions below to upgrade your PostgreSQL.
|
63 | 73 |
|
64 | 74 | * [CHANGE] The frontend component now does not cache results if it finds a `Cache-Control` header and if one of its values is `no-store`. #1974
|
65 |
| -* [FEATURE] Fan out parallelizable queries to backend queriers concurrently. |
66 |
| - * `-querier.sum-shards` (bool) |
67 |
| - * Requires a shard-compatible schema (v10+) |
68 |
| - * This causes the number of traces to increase accordingly. |
69 |
| - * The query-frontend now requires a schema config to determine how/when to shard queries, either from a file or from flags (i.e. by the `config-yaml` CLI flag). This is the same schema config the queriers consume. |
70 |
| - * It's also advised to increase downstream concurrency controls as well: |
71 |
| - * `querier.max-outstanding-requests-per-tenant` |
72 |
| - * `querier.max-query-parallelism` |
73 |
| - * `querier.max-concurrent` |
74 |
| - * `server.grpc-max-concurrent-streams` (for both query-frontends and queriers) |
75 |
| -* [ENHANCEMENT] metric `cortex_ingester_flush_reasons` gets a new `reason` value: `Spread`, when `-ingester.spread-flushes` option is enabled. |
76 | 75 | * [CHANGE] Flags changed with transition to upstream Prometheus rules manager:
|
77 | 76 | * `-ruler.client-timeout` is now `ruler.configs.client-timeout` in order to match `ruler.configs.url`.
|
78 | 77 | * `-ruler.group-timeout`has been removed.
|
|
0 commit comments