Separated filesystems for data and logs?


I'd like to know your thoughts on the best/recommended approach to organize the filesystem of a VM that will run an Elasticsearch instance.

How should I separate things in such a way for the service to have some degree od resilience if, let's say, the logs fill an entire disk?

I guess on first approach would be to separate "data" and "logs" in different partitions, so I can grow then separatedly...

So, what is the recommended filesystem configuration for a production ready Elasticsearch node?

Thank you

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.