From 6d7273fcca553746501b5b963dfdb02ee28dac40 Mon Sep 17 00:00:00 2001 From: timvisee Date: Tue, 30 Apr 2024 10:27:12 +0200 Subject: [PATCH] Resolve review comments --- qdrant-landing/content/documentation/guides/common-errors.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/qdrant-landing/content/documentation/guides/common-errors.md b/qdrant-landing/content/documentation/guides/common-errors.md index c5835e957..df030dc33 100644 --- a/qdrant-landing/content/documentation/guides/common-errors.md +++ b/qdrant-landing/content/documentation/guides/common-errors.md @@ -36,14 +36,15 @@ Please note, the command should be executed before you run Qdrant server. When starting a Qdrant instance as part of a distributed deployment, you may come across an error message similar to this: + ```bash Can't open Collections meta Wal: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" } ``` It means that Qdrant cannot start because a collection cannot be loaded. Its associated [WAL](../../concepts/storage/#versioning) files are currently -unavailable, likely because the very same files are already being used by -another Qdrant instance. +unavailable, likely because the same files are already being used by another +Qdrant instance. Each node must have their own separate storage directory, volume or mount.