You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ingester can now flush only specified users. (#4073)
* Ingester can now flush only specified users.
Signed-off-by: Peter Štibraný <peter.stibrany@grafana.com>
* Rename tenant to t, to shorten the query string.
Signed-off-by: Peter Štibraný <peter.stibrany@grafana.com>
* CHANGELOG.md and api updates.
Signed-off-by: Peter Štibraný <peter.stibrany@grafana.com>
* Remove nil/empty distinction.
Signed-off-by: Peter Štibraný <peter.stibrany@grafana.com>
* Review feedback.
Signed-off-by: Peter Štibraný <peter.stibrany@grafana.com>
* Fix documentation.
Signed-off-by: Peter Štibraný <peter.stibrany@grafana.com>
* Use allowed tenants for passing which tenants to flush.
Signed-off-by: Peter Štibraný <peter.stibrany@grafana.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,7 @@
39
39
*[ENHANCEMENT] Ingester: added following per-ingester (instance) limits: max number of series in memory (`-ingester.instance-limits.max-series`), max number of users in memory (`-ingester.instance-limits.max-tenants`), max ingestion rate (`-ingester.instance-limits.max-ingestion-rate`), and max inflight requests (`-ingester.instance-limits.max-inflight-push-requests`). These limits are only used when using blocks storage. Limits can also be configured using runtime-config feature, and current values are exported as `cortex_ingester_instance_limits` metric. #3992.
40
40
*[ENHANCEMENT] Cortex is now built with Go 1.16. #4062
41
41
*[ENHANCEMENT] Ruler: Added `-ruler.enabled-tenants` and `-ruler.disabled-tenants` to explicitly enable or disable rules processing for specific tenants. #4074
42
+
*[ENHANCEMENT] Block Storage Ingester: `/flush` now accepts two new parameters: `tenant` to specify tenant to flush and `wait=true` to make call synchronous. Multiple tenants can be specified by repeating `tenant` parameter. If no `tenant` is specified, all tenants are flushed, as before. #4073
42
43
*[BUGFIX] Ruler-API: fix bug where `/api/v1/rules/<namespace>/<group_name>` endpoint return `400` instead of `404`. #4013
43
44
*[BUGFIX] Distributor: reverted changes done to rate limiting in #3825. #3948
44
45
*[BUGFIX] Ingester: Fix race condition when opening and closing tsdb concurrently. #3959
Copy file name to clipboardExpand all lines: docs/api/_index.md
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -247,6 +247,10 @@ GET,POST /flush
247
247
248
248
Triggers a flush of the in-memory time series data (chunks or blocks) to the long-term storage. This endpoint triggers the flush also when `-ingester.flush-on-shutdown-with-wal-enabled` or `-blocks-storage.tsdb.flush-blocks-on-shutdown` are disabled.
249
249
250
+
When using blocks storage, this endpoint accepts `tenant` parameter to specify tenant whose blocks are compacted and shipped. This parameter may be specified multiple times to select more tenants. If no tenant is specified, all tenants are flushed.
251
+
252
+
Flush endpoint now also accepts `wait=true` parameter, which makes the call synchronous – it will only return after flushing has finished. Note that returned status code does not reflect the result of flush operation. This parameter is only available when using blocks storage.
0 commit comments