Note that after 60s by default, whatever the method you used, version number will restart from 1. Are you sure you did not hit this? Is it something you can reproduce with a script?
Note that you can control this period using settings.gc_deletes at index level. See https://gist.github.com/dadoonet/7704908 -- David Pilato | Technical Advocate | Elasticsearch.com @dadoonet | @elasticsearchfr Le 20 décembre 2013 at 09:37:23, Arjit Gupta ([email protected]) a écrit: Hi, I observed a version mis match when I run a deleteByQuery and when do a bulk delete by Id. So If I have a doc I want to search and delete it I have two option either use 1. deleteByQuery 2. Search the document and issue a bulk delete these both delete the documents ---- But when I index the document with same Id which was deleted deleteByQuery starts the indexing with version 1 where other (Search the document and issue a bulk delete) starts the indexing with lastVersion+1. Is this expected ? I am working on version 0.90.1 If I am not clear let me know. Thanks, Arjit -- 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 protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/28c9c248-25b9-4773-a6a8-878bd595c565%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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 protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/etPan.52b40f04.1d4ed43b.111%40MacBook-Air-de-David.local. For more options, visit https://groups.google.com/groups/opt_out.
