From afc6a6e2182e0c37f320500632170248a39892a1 Mon Sep 17 00:00:00 2001 From: Dmytro Kozlov Date: Thu, 9 Mar 2023 14:28:55 +0200 Subject: [PATCH] app/vmctl: follow up after 09e3742a827a36dead71569be9e971b82a75e243 (#3937) app/vmctl: follow up after 09e3742a827a36dead71569be9e971b82a75e243 --- app/vmctl/README.md | 2 ++ docs/CHANGELOG.md | 1 + docs/vmctl.md | 2 ++ 3 files changed, 5 insertions(+) diff --git a/app/vmctl/README.md b/app/vmctl/README.md index 8066c8db03..fd23c5ba56 100644 --- a/app/vmctl/README.md +++ b/app/vmctl/README.md @@ -788,6 +788,8 @@ Please note that each import request can load up to a single vCPU core on Victor to allocated CPU resources of your VictoriaMetrics installation. 8. `vmctl` supports `--vm-native-src-headers` and `--vm-native-dst-headers` which defines headers to send with each request to the corresponding source address. +9. `vmctl` supports `--vm-native-disable-http-keep-alive` to allow `vmctl` to use non-persistent HTTP connections to avoid +error `use of closed network connection` when run a longer export. In this mode `vmctl` acts as a proxy between two VM instances, where time series filtering is done by "source" (`src`) and processing is done by "destination" (`dst`). So no extra memory or CPU resources required on `vmctl` side. Only diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md index 2624b3c3d4..0f6dfd7763 100644 --- a/docs/CHANGELOG.md +++ b/docs/CHANGELOG.md @@ -20,6 +20,7 @@ The following tip changes can be tested by building VictoriaMetrics components f * FEATURE: [vmctl](https://docs.victoriametrics.com/vmctl.html): increase the default value for `--remote-read-http-timeout` command-line option from 30s (30 seconds) to 5m (5 minutes). This reduces the probability of timeout errors when migrating big number of time series. See [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/3879). * FEATURE: [vmctl](https://docs.victoriametrics.com/vmctl.html): migrate series one-by-one in [vm-native mode](https://docs.victoriametrics.com/vmctl.html#native-protocol). This allows better tracking the migration progress and resuming the migration process from the last migrated time series. See [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/3859) and [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3600). * FEATURE: [vmctl](https://docs.victoriametrics.com/vmctl.html): add `--vm-native-src-headers` and `--vm-native-dst-headers` command-line flags, which can be used for setting custom HTTP headers during [vm-native migration mode](https://docs.victoriametrics.com/vmctl.html#native-protocol). Thanks to @baconmania for [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/3906). +* FEATURE: [vmctl](https://docs.victoriametrics.com/vmctl.html): add `--vm-native-disable-http-keep-alive` command-line flags to allow `vmctl` to use non-persistent HTTP connections in [vm-native migration mode](https://docs.victoriametrics.com/vmctl.html#native-protocol). Thanks to @baconmania for [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/3909). * BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): fix panic when [writing data to Kafka](https://docs.victoriametrics.com/vmagent.html#writing-metrics-to-kafka). The panic has been introduced in [v1.88.0](https://docs.victoriametrics.com/CHANGELOG.html#v1880). * BUGFIX: prevent from possible `invalid memory address or nil pointer dereference` panic during [background merge](https://docs.victoriametrics.com/#storage). The issue has been introduced at [v1.85.0](https://docs.victoriametrics.com/CHANGELOG.html#v1850). See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3897). diff --git a/docs/vmctl.md b/docs/vmctl.md index 3d52712f7d..bfa2b91574 100644 --- a/docs/vmctl.md +++ b/docs/vmctl.md @@ -792,6 +792,8 @@ Please note that each import request can load up to a single vCPU core on Victor to allocated CPU resources of your VictoriaMetrics installation. 8. `vmctl` supports `--vm-native-src-headers` and `--vm-native-dst-headers` which defines headers to send with each request to the corresponding source address. +9. `vmctl` supports `--vm-native-disable-http-keep-alive` to allow `vmctl` to use non-persistent HTTP connections to avoid +error `use of closed network connection` when run a longer export. In this mode `vmctl` acts as a proxy between two VM instances, where time series filtering is done by "source" (`src`) and processing is done by "destination" (`dst`). So no extra memory or CPU resources required on `vmctl` side. Only