[erlang-questions] Disable MnesiaCore dump file generation
Jesper Louis Andersen
Mon May 22 21:43:30 CEST 2017
Let me add that it is often a good idea to separate your data directories
from your code directories. Preferably by volume and quota as well. While
here, establish logs isolated as well and make sure they are rotated so
they only use a limited amount of memory. If possible, enable disk_sup or
make a warning system so you can detect situations where you are about to
run low on disk through the alarm_handler.
On Mon, May 22, 2017 at 9:32 PM Dan Gudmundsson <dangud@REDACTED> wrote:
> You can set the core dir with the config parameter:
> erl -mnesia core_dir Directory
> On Mon, May 22, 2017 at 8:02 PM Sergey Safarov <s.safarov@REDACTED>
>> You can change working directory to separate volume with limited size. As
>> example mount to. /run/myapp directory "tmp" volume with size 10 Mbyte.
>> Then cd to /run/myapp
>> пн, 22 мая 2017, 13:21 Mithun B <mithunb@REDACTED>:
>>> Hi all,
>>> I have an application using Mnesia Database running is a memory
>>> constrained environment. So is there any way to disable MnesiaCore file
>>> creation by when something goes wrong with Mnesia which is a default
>>> case? Or is it possible to give limit on the size of file or constraint
>>> on count of files?
>>> Since the MnesiaCore file gets created with different name each
>>> time, it will not overwrite the previous one. It casuses flooding of
>>> MnesiaCore files in the working directory of my application, if the
>>> application has crashed for multiple times.
>>> Mithun B
>>> erlang-questions mailing list
>> erlang-questions mailing list
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions