VictoriaMetrics v1.42.0 Release Notes

Release Date: 2020-09-30 // over 3 years ago
  • 🔄 Changes since v1.41.1

    🔋 FEATURE: use all the available CPU cores when accepting data via a single TCP connection for all the supported protocols. Previously data ingested via a single TCP connection could use only a single CPU core. This could limit data ingestion performance. The main benefit of this feature is that data can be imported at max speed via a single connection - there is no need to open multiple concurrent connections to VictoriaMetrics or vmagent in order to achieve the maximum data ingestion speed.

    🔋 FEATURE: cluster: improve performance for data ingestion path from vminsert to vmstorage nodes. The maximum data ingestion performance for a single connection between vminsert and vmstorage node scales with the number of available CPU cores on vmstorage side. This should help with #791 .

    🔋 FEATURE: add ability to export / import data in native format via /api/v1/export/native and /api/v1/import/native. This is the most optimized approach for data migration between VictoriaMetrics instances. Both single-node and cluster instances are supported. See #787 (comment) .

    FEATURE: add reduce_mem_usage query option to /api/v1/export in order to reduce memory usage during data export / import. See these docs for details.

    🔋 FEATURE: improve performance for /api/v1/series handler when it returns big number of time series.

    🔀 FEATURE: add vm_merge_need_free_disk_space metric, which can be used for estimating the number of deferred background data merges due to the lack of free disk space. See #686 .

    🔋 FEATURE: add OpenBSD support. See #785 .

    🛠 BUGFIX: properly apply -search.maxStalenessInterval command-line flag value. See #784 .

    🛠 BUGFIX: fix displaying data in Grafana tables. See #720 .

    🛠 BUGFIX: do not adjust the number of detected CPU cores found at /sys/devices/system/cpu/online. The adjustment was increasing the resulting GOMAXPROC by 1, which looked confusing to users. See #685 (comment) .

    🛠 BUGFIX: vmagent: do not show -remoteWrite.url in initial logs if -remoteWrite.showURL isn't set. See #773 .

    🛠 BUGFIX: properly handle case when /metrics/find finds both a leaf and a node for the given query=prefix.*. In this case only the node must be returned with stripped dot in the end of id as carbonapi does.

    How to run VictoriaMetrics

    📄 Unpack the victoria-metrics-*.tar.gz archive and read these docs.

    vmutils-*.tag.gz archive contains the following tools:

    🐳 The corresponding docker images are available here.
    Cluster version is available here.

    🚀 vmctl releases are available here.