No description
Find a file
Artem Fetishev 6b9f57e5f7
lib/storage: Fix flaky test: TestStorageRotateIndexDB (#7267)
This commit fixes the TestStorageRotateIndexDB flaky test reported at:
#6977. Sample test failure: https://pastebin.com/bTSs8HP1

The test fails because one goroutine adds items to the indexDB table
while another goroutine is closing that table. This may happen if
indexDB rotation happens twice during one Storage.add() operation:
-  Storage.add() takes the current indexDB and adds index recods to it
- First index db rotation makes the current index DB a previous one
(still ok at this point)
- Second index db rotation removes the indexDB that was current two
rotations earlier. It does this by setting the mustDrop flag to true and
decrementing the ref counter. The ref counter reaches zero which cases
the underlying indexdb table to release its resources gracefully.
Graceful release assumes that the table is not written anymore. But
Storage.add() still adds items to it.

The solution is to increment the indexDB ref counters while it is used
inside add().
The unit test has been changed a little so that the test fails reliably.
The idea is to make add() function invocation to last much longer,
therefore the test inserts not just one record at a time but thouthands
of them.

To see the test fail, just replace the idbsLocked() func with:

```go
unc (s *Storage) idbsLocked2() (*indexDB, *indexDB, func()) {
       return s.idbCurr.Load(), s.idbNext.Load(), func() {}
}
``` 


---------

Signed-off-by: Artem Fetishev <rtm@victoriametrics.com>
2024-10-23 11:48:21 +02:00
.github Revert "deployment: build image for vmagent streamaggr benchmark (#6515)" 2024-07-16 13:27:06 +02:00
app app/vmalert: update -remoteWrite.concurrency and -remoteWrite.flushInterval (#7272) 2024-10-22 14:43:55 +02:00
cspell docs: fixes misspelled typos 2024-09-13 12:14:24 +02:00
dashboards dashboards: fix vmagent monitoring chart descriptions (#7283) 2024-10-17 12:12:47 +02:00
deployment docs/vmanomaly-release-1.17.2 (#7322) 2024-10-22 13:42:37 +03:00
docs docs: clarify that vminsert also supports exponential histogram parsing 2024-10-23 11:47:50 +02:00
lib lib/storage: Fix flaky test: TestStorageRotateIndexDB (#7267) 2024-10-23 11:48:21 +02:00
package simplify release process (#3012) 2022-08-31 02:27:24 +03:00
ports/OpenBSD docs: convert png images to webp in all the docs except of docs/operator/* 2023-11-22 19:21:00 +02:00
vendor app/vlogscli: add interactive command-line tool for querying VictoriaLogs 2024-10-01 12:23:07 +02:00
.dockerignore added packer build for DigitalOcean Droplets (#1917) 2021-12-21 12:09:14 +02:00
.gitignore testing: allow disabling fsync to make tests run faster (#6871) 2024-08-30 10:54:46 +02:00
.golangci.yml .golangci.yml: properly specify functions to exclude for return values check after the upgrade to v1.59.1 at 239a7b6e6f 2024-06-11 16:41:01 +02:00
.wwhrd.yml add MPL-2.0 to approved licenses 2024-08-29 10:35:36 +02:00
CODE_OF_CONDUCT.md A good change for MD files (#2353) 2022-03-22 13:40:55 +02:00
CONTRIBUTING.md Move CONTRIBUTING.md to docs/ 2024-04-20 23:11:22 +02:00
go.mod app/vlogscli: add interactive command-line tool for querying VictoriaLogs 2024-10-01 12:23:07 +02:00
go.sum app/vlogscli: add interactive command-line tool for querying VictoriaLogs 2024-10-01 12:23:07 +02:00
LICENSE LICENSE: update the current year from 2023 to 2024 2024-01-17 01:48:04 +02:00
Makefile app/vlogscli: add support for live tailing 2024-10-09 12:30:17 +02:00
README.md dox: fix anchor in github readme (#7160) 2024-10-03 10:39:57 +02:00
SECURITY.md add new LTS release v1.102.x 2024-08-02 11:12:20 +02:00
VM_logo.zip docs: update logos files and usage rules (#6980) 2024-09-24 11:53:58 +02:00

VictoriaMetrics

Latest Release Docker Pulls Slack GitHub license Go Report Build Status codecov

VictoriaMetrics logo

VictoriaMetrics is a fast, cost-saving, and scalable solution for monitoring and managing time series data. It delivers high performance and reliability, making it an ideal choice for businesses of all sizes.

Here are some resources and information about VictoriaMetrics:

Yes, we open-source both the single-node VictoriaMetrics and the cluster version.

Prominent features

VictoriaMetrics is optimized for timeseries data, even when old time series are constantly replaced by new ones at a high rate, it offers a lot of features:

Enterprise version

In addition, the Enterprise version includes extra features:

  • Anomaly detection: Automation and simplification of your alerting rules, covering complex anomalies found in metrics data.
  • Backup automation: Automates regular backup procedures.
  • Multiple retentions: Reducing storage costs by specifying different retentions for different datasets.
  • Downsampling: Reducing storage costs and increasing performance for queries over historical data.
  • Stable releases with long-term support lines (LTS).
  • Comprehensive support: First-class consulting, feature requests and technical support provided by the core VictoriaMetrics dev team.
  • Many other features, which you can read about on the Enterprise page.

Contact us if you need enterprise support for VictoriaMetrics. Or you can request a free trial license here, downloaded Enterprise binaries are available at Github Releases.

We strictly apply security measures in everything we do. VictoriaMetrics has achieved security certifications for Database Software Development and Software-Based Monitoring Services. See Security page for more details.

Benchmarks

Some good benchmarks VictoriaMetrics achieved:

Community and contributions

Feel free asking any questions regarding VictoriaMetrics:

If you like VictoriaMetrics and want to contribute, then please read these docs.

The provided ZIP file contains three folders with different logo orientations. Each folder includes the following file types:

  • JPEG: Preview files
  • PNG: Preview files with transparent background
  • AI: Adobe Illustrator files

VictoriaMetrics Logo Usage Guidelines

Font

  • Font Used: Lato Black
  • Download here: Lato Font

Color Palette

Logo Usage Rules

  • Only use the Lato Black font as specified.
  • Maintain sufficient clear space around the logo for visibility.
  • Do not modify the spacing, alignment, or positioning of design elements.
  • You may resize the logo as needed, but ensure all proportions remain intact.

Thank you for your cooperation!