This shows you the differences between two versions of the page.
Next revisionBoth sides next revision | |||
mission:log:2013:07:17:elasticsearch-garbage-collector [2013/07/17 11:51] – created chrono | mission:log:2013:07:17:elasticsearch-garbage-collector [2013/07/17 11:59] – [Elasticsearch Garbage Collector] chrono | ||
---|---|---|---|
Line 56: | Line 56: | ||
</ | </ | ||
- | It runs every 10 minutes (as a cron job) and checks the available space on the device where Elasticsearch stores its indices. In this example /logdata is mounted on /dev/md0. If md0 has less than 30gb of free diskspace it automagically finds the oldest Elasticsearch index and drops it via Elasticsearch' | + | It runs every 10 minutes (as a cron job) and checks the available space on the device where Elasticsearch stores its indices. In this example /logdata is mounted on /dev/md0. If md0 has less than 30GB of free diskspace it automagically finds the oldest Elasticsearch index and drops it via Elasticsearch' |
- | A simple locking mechanism will prevent multiple running instances in case of timing issues. All you need is curl for it to work and it will increase your storage efficiency so that you can always have as much past data available as your storage allows without the risk of full disk issues or manual maintaining. | + | A simple locking mechanism will prevent multiple running instances in case of timing issues. All you need is curl for it to work and it will increase your storage efficiency so that you can always have as much past data available as your storage allows without the risk of full disk issues or the hassle of manual |
{{tag> | {{tag> |