Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
ddobric opened this issue Jul 20, 2024 · 1 comment
Open

Comments

@ddobric
Copy link
Contributor

ddobric commented Jul 20, 2024

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 <your desired installation name> ./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?

@WiktorSobanski
Copy link

Hi @ddobric, were you able to figure it out?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants