mirror of
https://github.com/qdrant/landing_page.git
synced 2026-09-28 23:48:31 +02:00
Add FAQ for not being able to open collection WAL
This commit is contained in:
@@ -31,3 +31,24 @@ ulimit -n 10000
|
||||
```
|
||||
|
||||
Please note, the command should be executed before you run Qdrant server.
|
||||
|
||||
## Can't open Collections meta Wal
|
||||
|
||||
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.
|
||||
|
||||
Each node must have their own separate storage directory, volume or mount.
|
||||
|
||||
The formed cluster will take care of sharing all data with each node, putting it
|
||||
all in the correct places for you. If using Kubernetes, each node must have
|
||||
their own volume. If using Docker, each node must have their own storage mount
|
||||
or volume. If using Qdrant directly, each node must have their own storage
|
||||
directory.
|
||||
|
||||
Reference in New Issue
Block a user