We recently created a lot of (date suffixed) indexes (about 3,000) on our
development cluster (1.3.2). Subsequently we deleted many of these indexes.
The cluster ran, predominantly green, for several days, certainly more than
a week after that with no sign of the indexes. After that we performed a
cluster restart and the "recover dangling indexes" functionality
unexpectedly re-animated all of the deleted indexes. We (think) we
understand the dangling index recovery functionality (and could potentially
disable it - but not sure if we really want to go down that road though).
So, the question is, at what point does an index deleted through the API
get cleaned from individual node disks? At what stage will a deleted index
no longer be recovered as dangling? Is this zombie functionality by design?
Has a physical part of the delete failed in our cluster? Do we need silver
bullets to kill our indexes once and for all?
The extra problem we faced in this scenario is that the recovered indexes
placed our elected master under quite a bit of stress, rendering our
Thanks in advance for any insight,
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/fb2d385d-1143-48a0-97e5-0b1b90776723%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.