|
2 | 2 |
|
3 | 3 | ## master / unreleased |
4 | 4 |
|
| 5 | +* [CHANGE] Memberlist: Expose default configuration values to the command line options. Note that setting these explicitly to zero will no longer cause the default to be used. If the default is desired, then do set the option. The following are affected: #4276 |
| 6 | + - `-memberlist.stream-timeout` |
| 7 | + - `-memberlist.retransmit-factor` |
| 8 | + - `-memberlist.pull-push-interval` |
| 9 | + - `-memberlist.gossip-interval` |
| 10 | + - `-memberlist.gossip-nodes` |
| 11 | + - `-memberlist.gossip-to-dead-nodes-time` |
| 12 | + - `-memberlist.dead-node-reclaim-time` |
| 13 | +* [FEATURE] Ruler: Add new `-ruler.query-stats-enabled` which when enabled will report the `cortex_ruler_query_seconds_total` as a per-user metric that tracks the sum of the wall time of executing queries in the ruler in seconds. #4317 |
| 14 | +* [FEATURE] Query Frontend: Add `cortex_query_fetched_series_total` and `cortex_query_fetched_chunks_bytes_total` per-user counters to expose the number of series and bytes fetched as part of queries. These metrics can be enabled with the `-frontend.query-stats-enabled` flag (or its respective YAML config option `query_stats_enabled`). #4343 |
| 15 | +* [CHANGE] Update Go version to 1.16.6. #4362 |
| 16 | +* [CHANGE] Querier / ruler: Change `-querier.max-fetched-chunks-per-query` configuration to limit to maximum number of chunks that can be fetched in a single query. The number of chunks fetched by ingesters AND long-term storare combined should not exceed the value configured on `-querier.max-fetched-chunks-per-query`. #4260 |
| 17 | +* [CHANGE] Memberlist: the `memberlist_kv_store_value_bytes` has been removed due to values no longer being stored in-memory as encoded bytes. #4345 |
| 18 | +* [CHANGE] Prevent path traversal attack from users able to control the HTTP header `X-Scope-OrgID`. #4375 (CVE-2021-36157) |
| 19 | + * Users only have control of the HTTP header when Cortex is not frontend by an auth proxy validating the tenant IDs |
| 20 | +* [ENHANCEMENT] Add timeout for waiting on compactor to become ACTIVE in the ring. #4262 |
| 21 | +* [ENHANCEMENT] Reduce memory used by streaming queries, particularly in ruler. #4341 |
| 22 | +* [ENHANCEMENT] Ring: allow experimental configuration of disabling of heartbeat timeouts by setting the relevant configuration value to zero. Applies to the following: #4342 |
| 23 | + * `-distributor.ring.heartbeat-timeout` |
| 24 | + * `-ring.heartbeat-timeout` |
| 25 | + * `-ruler.ring.heartbeat-timeout` |
| 26 | + * `-alertmanager.sharding-ring.heartbeat-timeout` |
| 27 | + * `-compactor.ring.heartbeat-timeout` |
| 28 | + * `-store-gateway.sharding-ring.heartbeat-timeout` |
| 29 | +* [ENHANCEMENT] Ring: allow heartbeats to be explicitly disabled by setting the interval to zero. This is considered experimental. This applies to the following configuration options: #4344 |
| 30 | + * `-distributor.ring.heartbeat-period` |
| 31 | + * `-ingester.heartbeat-period` |
| 32 | + * `-ruler.ring.heartbeat-period` |
| 33 | + * `-alertmanager.sharding-ring.heartbeat-period` |
| 34 | + * `-compactor.ring.heartbeat-period` |
| 35 | + * `-store-gateway.sharding-ring.heartbeat-period` |
| 36 | +* [ENHANCEMENT] Memberlist: optimized receive path for processing ring state updates, to help reduce CPU utilization in large clusters. #4345 |
| 37 | +* [ENHANCEMENT] Memberlist: expose configuration of memberlist packet compression via `-memberlist.compression=enabled`. #4346 |
| 38 | +* [BUGFIX] HA Tracker: when cleaning up obsolete elected replicas from KV store, tracker didn't update number of cluster per user correctly. #4336 |
| 39 | +* [BUGFIX] Ruler: fixed counting of PromQL evaluation errors as user-errors when updating `cortex_ruler_queries_failed_total`. #4335 |
| 40 | + |
| 41 | + |
5 | 42 | ## 1.10.0 / 2021-08-03 |
6 | 43 |
|
7 | 44 | * [CHANGE] Prevent path traversal attack from users able to control the HTTP header `X-Scope-OrgID`. #4375 (CVE-2021-36157) |
|
0 commit comments