Azure-Samples / Azure-Samples/qdrant-azure

No space left on device: WAL buffer size exceeds available disk space

Open
#35 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
105
Forks
24
PR merge metrics
No merged PRs in 30d

Description

### This issue is for a:
```
- [ x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
```

### Minimal steps to reproduce
Install the **qdrant** to Azure by using the provided default helm script.

`helm install ./qdrant-on-azure --create-namespace`

Insert successively points to DB, like shown below in pseudo-code:

```
for(i=0;I<100000;)
{
InsertPoint(newPoint)
}

```
The function InserPoint is sending following payload to the URL:

`{{url}}collections/test/points?wait=true`

```
{
"points": [
{"id": 1, "vector": [0.05, 0.61, 0.76, 0.74], "payload": {"city": "Berlin" }}
]
}
```

All will work fine, and then after a few thousand records, the service will stop working.
The following error appears:

> "Service internal error: No space left on device: WAL buffer size exceeds available disk space".

The service is running on a VM inside an Azure pod with 128GB of disc space and is currently at 17% usage. This information is shown in the storage blade.

The problem also occurs when trying to query points. It seems that some log files might be full.
How do we figure out the issue here, and how do we fix it?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.