-
Notifications
You must be signed in to change notification settings - Fork 67
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
Zed service crash caused by large vacuum operation #4940
Labels
bug
Something isn't working
Comments
mattnibs
added a commit
that referenced
this issue
Jan 9, 2024
mattnibs
added a commit
that referenced
this issue
Jan 9, 2024
mattnibs
added a commit
that referenced
this issue
Jan 9, 2024
mattnibs
added a commit
that referenced
this issue
Jan 9, 2024
Verified in Zed commit a5ec530. After loading with 300k commits like before, I can now delete & vacuum without crashing.
Thanks @mattnibs! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tl;dr
A
zed serve
can be made to crash and exit if asked to vacuum 300k objects.Details
Repro is with Zed commit 59b72d8. I bumped into this issue while running tests related to #4934.
After starting a
zed serve
, I post 300k objects as separate commits using the record-poster tool. Then I delete all but 5 of the records, compact the pool, and initiate a vacuum to clean up the storage consumed by the deleted data.At this point I find the
zed serve
process has generated the contents of the large/attached dump.txt.gz and exited. Here's a brief excerpt of the very top of the dump:My notes indicate I originally reproduced the problem after having only posted 100k objects. On a more recent attempt with 100k it didn't repro, but it's repro'ed reliably every time with 300k. I also recognize this is a particularly abusive test, but the community zync user I was helping with #4934 had a pool with about 12k objects to vacuum, so this test isn't too far off from what we might experience in the wild.
The text was updated successfully, but these errors were encountered: