VictoriaMetrics/app/vminsert/common
Aliaksandr Valialkin d577657fb7
lib/streamaggr: follow-up for ff72ca14b9
- Make sure that the last successfully loaded config is used on hot-reload failure
- Properly cleanup resources occupied by already initialized aggregators
  when the current aggregator fails to be initialized
- Expose distinct vmagent_streamaggr_config_reload* metrics per each -remoteWrite.streamAggr.config
  This should simplify monitoring and debugging failed reloads
- Remove race condition at app/vminsert/common.MustStopStreamAggr when calling sa.MustStop() while sa
  could be in use at realoadSaConfig()
- Remove lib/streamaggr.aggregator.hasState global variable, since it may negatively impact scalability
  on system with big number of CPU cores at hasState.Store(true) call inside aggregator.Push().
- Remove fine-grained aggregator reload - reload all the aggregators on config change instead.
  This simplifies the code a bit. The fine-grained aggregator reload may be returned back
  if there will be demand from real users for it.
- Check -relabelConfig and -streamAggr.config files when single-node VictoriaMetrics runs with -dryRun flag
- Return back accidentally removed changelog for v1.87.4 at docs/CHANGELOG.md

Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3639
2023-03-31 22:30:38 -07:00
..
insert_ctx.go lib/streamaggr: follow-up for ff72ca14b9 2023-03-31 22:30:38 -07:00
insert_ctx_pool.go all: properly handle CPU limits set on the host system/container 2020-12-08 21:07:29 +02:00
sort_labels.go app/{vminsert,vmagent}: add -sortLabels command-line option for sorting time series labels before ingesting them in the storage 2021-03-31 23:27:58 +03:00
streamaggr.go lib/streamaggr: follow-up for ff72ca14b9 2023-03-31 22:30:38 -07:00