mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2026-06-16 15:23:05 +03:00
93bbe10074
This commit adds support for overriding vmstorage `maxUniqueTimeseries` with specific resource limits: 1. `-search.maxLabelsAPISeries` for [/api/v1/labels](https://docs.victoriametrics.com/url-examples/#apiv1labels), [/api/v1/label/.../values](https://docs.victoriametrics.com/url-examples/#apiv1labelvalues) 2. `-search. maxSeries` for [/api/v1/series](https://docs.victoriametrics.com/url-examples/#apiv1series) 3. `-search.maxTSDBStatusSeries` for [/api/v1/status/tsdb](https://docs.victoriametrics.com/#tsdb-stats) 4. `-search.maxDeleteSeries` for [/api/v1/admin/tsdb/delete_series](https://docs.victoriametrics.com/url-examples/#apiv1admintsdbdelete_series) Currently, this limit priority logic cannot be applied to flags `-search.maxFederateSeries` and `-search.maxExportSeries`, because they share the same RPC `search_v7` with the /api/v1/query and /api/v1/query_range APIs, preventing vmstorage from identifying the actual API of the request. To address that, we need to add additional information to the protocol between vmstorage and vmselect, which should be introduced in the future when possible. Related issue: https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7857