People make indices and forget about them. This is ok, but they still consume resources. Even if they never uploaded a document, the elastic 'shard' apparently still consumes memory. But apparently you can 'close' an index [https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-close]
Suggested actions:
- When "archiving" an index, also close it on elastic (maybe this already happens?)
- Run a housekeeping script:
- any index not accessed for X days is automatically archived, with an email sent to the owner(s) that their index is archived and might be deleted at some point [Gemini said: Method: Use the _stats API to check last_access_time or look at the creation_date ]
- any archived index not accessed for Y more days (e.g. 1 year?) is actually deleted after at least two mails to the owner. Ideally we first dump it do disk
- add an option to a project that prevents it from getting archived / autodeleted, perhaps only settable by server ADMIN?
People make indices and forget about them. This is ok, but they still consume resources. Even if they never uploaded a document, the elastic 'shard' apparently still consumes memory. But apparently you can 'close' an index [https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-close]
Suggested actions: