MongoDB crashing
Received an alert that my MongoDB service crashed and the redeploy failed. Anyone else seeing this issue?
Solution:Jump to solution
I was able to resolve it by growing the disk to the size allowed by my plan (had deployed it prior to upgrading)
22 Replies
Project ID:
5e567fcd-cbdc-4a7a-a47b-7fe40f7035b9
5e567fcd-cbdc-4a7a-a47b-7fe40f7035b9
Didn't change any of the default configs
deployment logs please https://bookmarklets.up.railway.app/log-downloader/
Here you go.
can you show me a screenshot of your memory metrics throughout all this?
They were flat at ~150 MB
what about disk usage?
It's not showing an disk usage metrics
does your mongodb not have a volume?
sorry was looking in the wrong spot, disk usage looks ok too
looks like mongo just crashed into an unrecoverable state, have you deployed a new mongodb since and restored a backup?
no but I will try that
Solution
I was able to resolve it by growing the disk to the size allowed by my plan (had deployed it prior to upgrading)
ah thats interesting, what plan did you have prior?
It was on the Hobby tier (500 MB disk) and I upgraded to Pro (50 GB disk)
Thanks for your help
hobby allows for 5gb volumes, trial and free allow for 500mb volumes, your graph doesnt come close to either of those limits, thats why this is odd
but hey, if its solved, its solved
There was mention of it trying to do a migration in the logs and the service not having access to full memory capacity. I think it may have been hitting some kind of limit during that
maybe a disk allocation that it couldnt do
will keep this in mind for anyone with similar problems, thanks!
this has happened to me multiple times for no apparent reason. my database barely had any data in it at all.