This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
mission:log:2013:07:17:elasticsearch-garbage-collector [2013/07/17 11:59] – [Elasticsearch Garbage Collector] chrono | mission:log:2013:07:17:elasticsearch-garbage-collector [2013/07/17 14:45] – [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 | + | 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 /dev/ |
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 monitoring & 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 monitoring & maintaining. |