mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-15 08:23:34 +01:00
91379331eb
This case is possible after the following steps:
1. vmagent successfully performed handshake with the -remoteWrite.url and the remote storage supports zstd-compressed data.
2. remote storage became unavailable or slow to ingest data, vmagent compressed the collected data into blocks with zstd and puts these blocks to persistent queue on disk.
3. vmagent restarts and the remote storage is unavailable during the handshake, then vmagent falls back to Snappy compression.
4. vmagent starts sending zstd-compressed data from persistent queue to the remote storage, while falsely advertizing it sends Snappy-compressed data.
5. The remote storage receives zstd-compressed data and fails unpacking it with Snappy.
The solution is the same as
|
||
|---|---|---|
| .. | ||
| clusternative/stream | ||
| common | ||
| csvimport | ||
| datadog | ||
| graphite | ||
| influx | ||
| native/stream | ||
| newrelic | ||
| opentelemetry | ||
| opentsdb | ||
| opentsdbhttp | ||
| prometheus | ||
| promremotewrite/stream | ||
| vmimport | ||