I am testing the following couchbase version: 4.5.0-2203 Enterprise Edition (build-2203).
Regardless of the reason, there is a particular process that seems to crash often. Every time this service crash, couchbase creates core files in the /opt/couchbase/var/lib/couchbase folder.
-rw------- 1 couchbase couchbase 1210572800 May 9 15:13 core.2295
-rw------- 1 couchbase couchbase 1584775168 May 9 15:14 core.2322
-rw------- 1 couchbase couchbase 1925439488 May 9 15:16 core.2345
My / is currently set to 8GIG total, with avg fee space of 4.2GIG. As you can see, the space usage drop very quickly.
My issue is not the process crashing, but rather the core files generation space.
-Is there best practices I should follow regarding disk space with couchbase?
-Should I have a dedicated mount for something else than data and index ?
ex, should I have a dedicated mount for /opt/couchbase/var/lib/couchbase?
-Is there a max value I can set in couchbase to limit the space generated by core files?
-Is there a rotation process I should put in place? If so, which files should be rotated?
-What size I should dedicate for couchbase logs? as you can see above 4GIG is clearly not enough.