Allow setting ttl at index level

[tsouza]

Allow setting ttl to index, so the whole index gets deleted when expired

[timbunce]

+1 for this, or something like it.

[philfreo]

+1 this would especially be useful for Marvel

[svenmeys]

+1 Definately a keeper. Also for marvel

[michelem09]

+1 especially for Marvel

[kimchy]

my thoughts are that we will allow to register custom operations to be executed against an index, after a specific time has passed. Deleting an index is one thing, another is optimizing it, changing its allocation attributed, unloading bloom filters, ... .

Side note, have you looked at curator? Its an external tool that can execute those actions.

[glongman]

+1 to "register custom actions"

[clintongormley]

Given that the Curator tool now exists (https://github.com/elasticsearch/curator) and is easy to use, closing this issue.

[gdeconto]

+1 especially for marvel

[yehosef]

Since it seems most of the people needing this are mentioning marvel - I'll add a comment. If I'm using a product that is monitoring the health of my search servers, especially one that you pay for for production, it shouldn't require me to install and configure another tool to keep it from crashing the server. The default config of marvel will eventually consume all the disk space. Marvel is making the log files, I should configure the clean up through there. If you want to install and use curator with marvel, that's fine. But we should have an interface to manage how long we want to keep archives or settings to automatically delete when the remaining space gets to (...)

[chrisinmtown]

Suggest reopening this issue. I agree strongly with @yehosef bcos it's surprising to find Marvel steadily filling the disk. Suggest default setting should be expiration & auto deletion after 7 days (not infinity).

[glongman]

+1

[blackside]

+1

[photofinale]

+1

[casieowen]

+1. Please! Yes, curator can do it, but it's way more efficient to set a ttl on the index at time of creation!