Nothing seems to trigger it - i have a cluster of 4 x 8GB - so i don’t think it’s the resources. But every now and then the dash reports a 503 and my services become unresponsive.
I have to recycle the nodes before anything comes back up
Has anyone else seen this?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Greetings!
I’m sorry about the trouble this is causing for you. My instinct is that this is a memory issue, but it’s hard to prove. It’s just that this is so commonly the reason for similar scenarios that it is very reasonable to assume it first. You may want to check logs on one of the application servers to see if this is in fact the case. Here’s a quick read on the OOM killer, which is what I suspect to be the cause:
If you find that it isn’t the cause, I would try to see what layer this is occurring at. Would it be that one of the nodes is actually not responding on network at all, or just that the application is not responding? If the first, there may be a larger conversation. If the second, it may be worth reviewing the logs generated by the application.
Jarland
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.