Open dandrestor opened 6 years ago
👍 for this feature.
I haven't figured out a way to use curator to reliably shrink indices when you have a hot/warm architecture(without a dedicated shrink node). It is very common that a hot node will have more space than warm nodes, after the shards have migrated away. This is ok, except if curator selects an index which is sitting in a warm node. When that happens, it tries to move the index to a given hot node. Elasticsearch will now have a conflicting allocation, we asked for a specific node, which is not a 'warm' node.
Plus 💯 for this request. @outworlder comment describes our situation too
The title pretty much says it all. It would be nice to be able to do something like:
Could also be useful to have an
include_attribute
as well. May also apply to other actions also. Perhaps it's a good idea to decouple the node filters from the shrink action?