Brian,
Thanks for your effort, but I'm not talking about expired documents (as in
TTL) but actually and manually deleted ones (as described in my previous
questionhttps://groups.google.com/d/msg/elasticsearch/IU0b09LYs98/Z8ysJe9wdmEJ).
Deleted documents are still considered for optimistic locking purposes. By
default, they are fully expunged after 60s (index.gc_deletes). But as this
behaviour/setting isn't well documented, I'm looking for answers here.
This is useful if operations appear out of order (e.g. index v1, delete v3,
index v2). As I said, it does work. All I'm trying to figure out is how
reliable it is or what other settings I might temporarily change (e.g.
disabling optimizations).
My usecase is a tool that synchronizes indices to facilitate upgrades with
zero downtime https://github.com/molindo/molindo-elasticsync.
Thanks, Stefan
--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.