From eeea40241405faa6ce05f674eff174656340ce4f Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Tue, 4 Jul 2023 13:19:14 -0700 Subject: [PATCH] docs/Single-server-VictoriaMetrics.md: fix link to Storage section after the ab2d184e429140ff2fffe692636d830fad421ff4 --- README.md | 2 +- docs/README.md | 2 +- docs/Single-server-VictoriaMetrics.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index dff27fe66..3c1777078 100644 --- a/README.md +++ b/README.md @@ -1589,7 +1589,7 @@ Each partition consists of one or more **data parts**. Data parts outside the co are **eventually deleted** during [background merge](https://medium.com/@valyala/how-victoriametrics-makes-instant-snapshots-for-multi-terabyte-time-series-data-e1f3fb0e0282). The time range covered by data part is **not limited by retention period unit**. One data part can cover hours or days of data. Hence, a data part can be deleted only **when fully outside the configured retention**. -See more about partitions and parts [here](#Storage). +See more about partitions and parts [here](#storage). The maximum disk space usage for a given `-retentionPeriod` is going to be (`-retentionPeriod` + 1) months. For example, if `-retentionPeriod` is set to 1, data for January is deleted on March 1st. diff --git a/docs/README.md b/docs/README.md index 290bb47eb..6a4edb74e 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1592,7 +1592,7 @@ Each partition consists of one or more **data parts**. Data parts outside the co are **eventually deleted** during [background merge](https://medium.com/@valyala/how-victoriametrics-makes-instant-snapshots-for-multi-terabyte-time-series-data-e1f3fb0e0282). The time range covered by data part is **not limited by retention period unit**. One data part can cover hours or days of data. Hence, a data part can be deleted only **when fully outside the configured retention**. -See more about partitions and parts [here](#Storage). +See more about partitions and parts [here](#storage). The maximum disk space usage for a given `-retentionPeriod` is going to be (`-retentionPeriod` + 1) months. For example, if `-retentionPeriod` is set to 1, data for January is deleted on March 1st. diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index e410aedf9..3cdce022b 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -1600,7 +1600,7 @@ Each partition consists of one or more **data parts**. Data parts outside the co are **eventually deleted** during [background merge](https://medium.com/@valyala/how-victoriametrics-makes-instant-snapshots-for-multi-terabyte-time-series-data-e1f3fb0e0282). The time range covered by data part is **not limited by retention period unit**. One data part can cover hours or days of data. Hence, a data part can be deleted only **when fully outside the configured retention**. -See more about partitions and parts [here](#Storage). +See more about partitions and parts [here](#storage). The maximum disk space usage for a given `-retentionPeriod` is going to be (`-retentionPeriod` + 1) months. For example, if `-retentionPeriod` is set to 1, data for January is deleted on March 1st.