mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-23 20:37:12 +01:00
84fb59b0ba
This makes consitent the list of deleted metricIDs when it is used from both the current indexDB and the previous indexDB (aka extDB). This should fix the issue, which could lead to storing new samples under deleted metricIDs after indexDB rotation. See more details at https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1347#issuecomment-861232136 . Thanks to @tangqipengleoo for the initial analysis and the pull request - https://github.com/VictoriaMetrics/VictoriaMetrics/pull/1383 . This commit resolves the issue in more generic way compared to https://github.com/VictoriaMetrics/VictoriaMetrics/pull/1383 . The downside of the commit is the deletedMetricIDs set isn't cleaned from the metricIDs outside the retention. It needs app restart. This should be OK in most cases. |
||
|---|---|---|
| .. | ||
| Articles.md | ||
| BestPractices.md | ||
| CaseStudies.md | ||
| CHANGELOG.md | ||
| Cluster-VictoriaMetrics.md | ||
| FAQ.md | ||
| latest.png | ||
| logo.png | ||
| MetricsQL.md | ||
| per-tenant-stats.jpg | ||
| PerTenantStatistic.md | ||
| Quick-Start.md | ||
| Release-Guide.md | ||
| robots.txt | ||
| root.png | ||
| rp_daily_1.png | ||
| rp_daily_2.png | ||
| SampleSizeCalculations.md | ||
| Single-server-VictoriaMetrics.md | ||
| vmagent.md | ||
| vmagent.png | ||
| vmalert.md | ||
| vmauth.md | ||
| vmbackup.md | ||
| vmbackupmanager.md | ||
| vmctl.md | ||
| vmgateway-access-control.jpg | ||
| vmgateway-overview.jpeg | ||
| vmgateway-rate-limiting.jpg | ||
| vmgateway.md | ||
| vmrestore.md | ||
