From 6775a006228cfa51e039ed0f5c5a63da3d9833d9 Mon Sep 17 00:00:00 2001 From: hagen1778 Date: Wed, 26 Jun 2024 11:10:42 +0200 Subject: [PATCH] docs: rm mentions of `vmrecover` as it still doesn't exist While there, add a hint about truncated error messages. Signed-off-by: hagen1778 --- README.md | 3 ++- docs/README.md | 3 ++- docs/Single-server-VictoriaMetrics.md | 3 ++- 3 files changed, 6 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 60a781186..b551c2b7c 100644 --- a/README.md +++ b/README.md @@ -2430,7 +2430,8 @@ and [cardinality explorer docs](#cardinality-explorer). * If VictoriaMetrics doesn't work because of certain parts are corrupted due to disk errors, then just remove directories with broken parts. It is safe removing subdirectories under `<-storageDataPath>/data/{big,small}/YYYY_MM` directories when VictoriaMetrics isn't running. This recovers VictoriaMetrics at the cost of data loss stored in the deleted broken parts. - In the future, `vmrecover` tool will be created for automatic recovering from such errors. + The names of broken parts should be present in the error message. If you see that error message is truncated and doesn't contain all the information + try increasing `-loggerMaxArgLen` cmd-line flag to higher values to avoid error messages truncation. * If you see gaps on the graphs, try resetting the cache by sending request to `/internal/resetRollupResultCache`. If this removes gaps on the graphs, then it is likely data with timestamps older than `-search.cacheTimestampOffset` diff --git a/docs/README.md b/docs/README.md index de256da06..d5ec365de 100644 --- a/docs/README.md +++ b/docs/README.md @@ -2433,7 +2433,8 @@ and [cardinality explorer docs](#cardinality-explorer). * If VictoriaMetrics doesn't work because of certain parts are corrupted due to disk errors, then just remove directories with broken parts. It is safe removing subdirectories under `<-storageDataPath>/data/{big,small}/YYYY_MM` directories when VictoriaMetrics isn't running. This recovers VictoriaMetrics at the cost of data loss stored in the deleted broken parts. - In the future, `vmrecover` tool will be created for automatic recovering from such errors. + The names of broken parts should be present in the error message. If you see that error message is truncated and doesn't contain all the information + try increasing `-loggerMaxArgLen` cmd-line flag to higher values to avoid error messages truncation. * If you see gaps on the graphs, try resetting the cache by sending request to `/internal/resetRollupResultCache`. If this removes gaps on the graphs, then it is likely data with timestamps older than `-search.cacheTimestampOffset` diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index 315cf3e2d..1536a9b72 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -2441,7 +2441,8 @@ and [cardinality explorer docs](#cardinality-explorer). * If VictoriaMetrics doesn't work because of certain parts are corrupted due to disk errors, then just remove directories with broken parts. It is safe removing subdirectories under `<-storageDataPath>/data/{big,small}/YYYY_MM` directories when VictoriaMetrics isn't running. This recovers VictoriaMetrics at the cost of data loss stored in the deleted broken parts. - In the future, `vmrecover` tool will be created for automatic recovering from such errors. + The names of broken parts should be present in the error message. If you see that error message is truncated and doesn't contain all the information + try increasing `-loggerMaxArgLen` cmd-line flag to higher values to avoid error messages truncation. * If you see gaps on the graphs, try resetting the cache by sending request to `/internal/resetRollupResultCache`. If this removes gaps on the graphs, then it is likely data with timestamps older than `-search.cacheTimestampOffset`