-
-
Notifications
You must be signed in to change notification settings - Fork 126
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
[bug]: OOM killer on stalwart-email when importing accounts #406
Comments
I freed up a bit more RAM and it was able to complete. Seems like the sweet spot was pretty close to 4G.
|
Hi, Will investigate this. I have a few questions:
Stalwart only keeps messages in memory temporarily to parse them, so if there are multiple concurrent sessions uploading messages this might use all your available memory. Regular accounts have a concurrency limit but the import is done using a super user account where no limits are set. |
I'm not intimately familiar with the export format. Looks to me like
I don't know how many concurrent threads I was using on import. My command looked like this:
I only ran one of those processes at a time, one for each account. |
What happened?
I'm working on migrating from v0.5.3 to 0.7.3. I've exported my accounts individually. I'm working on importing one export of 10G of mailbox on a Virtual Private Server with 8G of RAM. I've freed up 4G of RAM to do the import. I'm still hitting OOM killer on the server process. I'm not sure if this means we need the full size of an import in available RAM in order to complete it, or if there's some kind of bug I've hit.
How can we reproduce the problem?
I can reproduce the problem by doing the following steps:
Version
v0.7.x
What database are you using?
RocksDB
What blob storage are you using?
RocksDB
Where is your directory located?
Internal
What operating system are you using?
Linux
Relevant log output
Failed to import emailId ee1aaabiyj: Transport error: error sending request for url (http://anasazi.theribbles.org:8080/jmap/upload/a/): error trying to connect: tcp connect error: Connection refused (os error 111)
The text was updated successfully, but these errors were encountered: