mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-21 14:44:00 +00:00
7094fa38bc
Previously all the newly ingested time series were registered in global `MetricName -> TSID` index.
This index was used during data ingestion for locating the TSID (internal series id)
for the given canonical metric name (the canonical metric name consists of metric name plus all its labels sorted by label names).
The `MetricName -> TSID` index is stored on disk in order to make sure that the data
isn't lost on VictoriaMetrics restart or unclean shutdown.
The lookup in this index is relatively slow, since VictoriaMetrics needs to read the corresponding
data block from disk, unpack it, put the unpacked block into `indexdb/dataBlocks` cache,
and then search for the given `MetricName -> TSID` entry there. So VictoriaMetrics
uses in-memory cache for speeding up the lookup for active time series.
This cache is named `storage/tsid`. If this cache capacity is enough for all the currently ingested
active time series, then VictoriaMetrics works fast, since it doesn't need to read the data from disk.
VictoriaMetrics starts reading data from `MetricName -> TSID` on-disk index in the following cases:
- If `storage/tsid` cache capacity isn't enough for active time series.
Then just increase available memory for VictoriaMetrics or reduce the number of active time series
ingested into VictoriaMetrics.
- If new time series is ingested into VictoriaMetrics. In this case it cannot find
the needed entry in the `storage/tsid` cache, so it needs to consult on-disk `MetricName -> TSID` index,
since it doesn't know that the index has no the corresponding entry too.
This is a typical event under high churn rate, when old time series are constantly substituted
with new time series.
Reading the data from `MetricName -> TSID` index is slow, so inserts, which lead to reading this index,
are counted as slow inserts, and they can be monitored via `vm_slow_row_inserts_total` metric exposed by VictoriaMetrics.
Prior to this commit the `MetricName -> TSID` index was global, e.g. it contained entries sorted by `MetricName`
for all the time series ever ingested into VictoriaMetrics during the configured -retentionPeriod.
This index can become very large under high churn rate and long retention. VictoriaMetrics
caches data from this index in `indexdb/dataBlocks` in-memory cache for speeding up index lookups.
The `indexdb/dataBlocks` cache may occupy significant share of available memory for storing
recently accessed blocks at `MetricName -> TSID` index when searching for newly ingested time series.
This commit switches from global `MetricName -> TSID` index to per-day index. This allows significantly
reducing the amounts of data, which needs to be cached in `indexdb/dataBlocks`, since now VictoriaMetrics
consults only the index for the current day when new time series is ingested into it.
The downside of this change is increased indexdb size on disk for workloads without high churn rate,
e.g. with static time series, which do no change over time, since now VictoriaMetrics needs to store
identical `MetricName -> TSID` entries for static time series for every day.
This change removes an optimization for reducing CPU and disk IO spikes at indexdb rotation,
since it didn't work correctly - see https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1401 .
At the same time the change fixes the issue, which could result in lost access to time series,
which stop receving new samples during the first hour after indexdb rotation - see https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2698
The issue with the increased CPU and disk IO usage during indexdb rotation will be addressed
in a separate commit according to https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1401#issuecomment-1553488685
This is a follow-up for
|
||
|---|---|---|
| .. | ||
| block.go | ||
| block_header.go | ||
| block_header_test.go | ||
| block_stream_merger.go | ||
| block_stream_reader.go | ||
| block_stream_reader_test.go | ||
| block_stream_reader_timing_test.go | ||
| block_stream_writer.go | ||
| block_stream_writer_timing_test.go | ||
| block_test.go | ||
| dedup.go | ||
| dedup_test.go | ||
| dedup_timing_test.go | ||
| filenames.go | ||
| index_db.go | ||
| index_db_test.go | ||
| index_db_timing_test.go | ||
| inmemory_part.go | ||
| inmemory_part_test.go | ||
| inmemory_part_timing_test.go | ||
| merge.go | ||
| merge_test.go | ||
| merge_timing_test.go | ||
| metaindex_row.go | ||
| metaindex_row_test.go | ||
| metric_name.go | ||
| metric_name_test.go | ||
| part.go | ||
| part_header.go | ||
| part_search.go | ||
| part_search_test.go | ||
| part_search_timing_test.go | ||
| partition.go | ||
| partition_search.go | ||
| partition_search_test.go | ||
| partition_test.go | ||
| raw_block.go | ||
| raw_row.go | ||
| search.go | ||
| search_test.go | ||
| storage.go | ||
| storage_test.go | ||
| storage_timing_test.go | ||
| table.go | ||
| table_search.go | ||
| table_search_test.go | ||
| table_search_timing_test.go | ||
| table_test.go | ||
| table_timing_test.go | ||
| tag_filters.go | ||
| tag_filters_test.go | ||
| tag_filters_timing_test.go | ||
| time.go | ||
| time_test.go | ||
| tsid.go | ||
| tsid_test.go | ||