Home / Companies / Aerospike / Blog / Post Details
Content Deep Dive

Determine root cause of Aerospike stop-writes in a new simple command

Blog post from Aerospike

Post Details
Company
Date Published
Author
-
Word Count
579
Company Posts That Month
2
Language
English
Hacker News Points
-
Post removed?
No
Summary

To avoid the devastating impact of Out Of Memory (OOM) errors in databases, Aerospike introduces a protective measure called the stop-writes condition, which acts as a sentinel to prevent database unrecoverable states. The `show stop-writes` command is introduced to help navigate through stop-writes scenarios and ensure data safety. Various configurations can trigger stop-writes, including restricting set sizes or namespace limits. When encountering stop-writes, using the `asadm` tool with its `manage config` command allows for temporary solutions, such as raising thresholds or freeing up space, until a more permanent fix is implemented.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Observability 1 1,228 220 86 -7%
OpenTelemetry 1 277 33 16 +123%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.