Skip to content
Visit booth 3171 at Google Cloud Next to see how to unlock real-time decisions at scaleMore info

Node problems

Out of Memory

If a crash has occurred without a stack trace, run dmesg to find out if asd was killed due to out of memory (OOM). In a typical scenario, the clients are writing too fast for too long. This can eventually cause a memory crash if the eviction rate isn’t set high enough. If you were experiencing a short term flood of traffic, the problem should correct itself after the evictions catch up. However, if your traffic has simply been growing over a long period of time, you should do a capacity check to see if you should increase the amount of memory in your nodes or the number of nodes in your cluster.

Also inspect /var/log/messages to see any relevant information.

In addition, get the machine’s uptime to confirm that the server did not go into an unexpected/undetected reboot. This has been known to happen, particularly in cloud environments.

Feedback

Was this page helpful?

What type of feedback are you giving?

What would you like us to know?

+Capture screenshot

Can we reach out to you?