- [ 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.
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?
This issue is for a:
Minimal steps to reproduce
Install the qdrant to Azure by using the provided default helm script.
helm install <your desired installation name> ./qdrant-on-azure --create-namespace
Insert successively points to DB, like shown below in pseudo-code:
The function InserPoint is sending following payload to the URL:
{{url}}collections/test/points?wait=true
All will work fine, and then after a few thousand records, the service will stop working. The following error appears:
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?