github-mirrors/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2024-11-21 14:44:00 +00:00
Code Issues Projects Releases Packages Wiki Activity

docs/Single-server-VictoriaMetrics.md: add a chapter about data updates

Browse source
This commit is contained in:
Aliaksandr Valialkin 2020-08-04 13:53:52 +03:00
parent 8cc2e01386
commit 265206a6c3
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
docs/Single-server-VictoriaMetrics.md
View file

@ -130,6 +130,7 @@ See [features available for enterprise customers](https://github.com/VictoriaMet
* [Monitoring](#monitoring) * [Monitoring](#monitoring)
* [Troubleshooting](#troubleshooting) * [Troubleshooting](#troubleshooting)
* [Backfilling](#backfilling) * [Backfilling](#backfilling)
* [Data updates](#data-updates)
* [Replication](#replication) * [Replication](#replication)
* [Backups](#backups) * [Backups](#backups)
* [Profiling](#profiling) * [Profiling](#profiling)
@ -1077,6 +1078,14 @@ Yet another solution is to increase `-search.cacheTimestampOffset` flag value in
for data with timestamps close to the current time. for data with timestamps close to the current time.
### Data updates
VictoriaMetrics doesn't support updating already exiting sample values to new ones. It stores all the ingested data points
for the same time series with identical timestamps. While is possible substituting old time series with new time series via
[removal of old time series](#how-to-delete-timeseries) and then [writing new time series](#backfilling), this approach
should be used only for one-off updates. It shouldn't be used for frequent updates because of non-zero overhead related to data removal.
### Replication ### Replication
Single-node VictoriaMetrics doesn't support application-level replication. Use cluster version instead. Single-node VictoriaMetrics doesn't support application-level replication. Use cluster version instead.