DocumentMissingException ScanScroll

Elastic Stack Elasticsearch
1

Hi

Client JavaAPI
Version 1.2.1
Requests: bulk
(no parent child mapping)
Does use nested structure.

Using scan and scroll to populate thousands (maybe millions) of delete
requests. It works like this:

Scan Search (for all documents with field f = 'the value')

Scroll in batches of say 1000:
create bulk delete requests and execute;
repeat until the end

This used to work no problem.

But now giving apparently random DocumentMissingException

Can't think why this might happen.

The mappings have been added to over time. Would that matter? I have heard
of the need to re-index.

I'm not even sure if the DocumentMissingException meant that the document
was there initially.

It could be a bug in the code. But it's single threaded and I can't see
how, if the document was there during the scan it's not there at the delete?

Anybody suggest what might be happening?

Obvious workaround is to simply ignore DocumentMissingException on delete
.. but why

Thanks.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/0ccf1a0e-418e-4002-9c74-ba10e20b7dfd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

yikes found it!

But in my code, ES is fine!

On Saturday, November 29, 2014 12:08:19 PM UTC, eune...@gmail.com wrote:

Hi

Client JavaAPI
Version 1.2.1
Requests: bulk
(no parent child mapping)
Does use nested structure.

Using scan and scroll to populate thousands (maybe millions) of delete
requests. It works like this:

Scan Search (for all documents with field f = 'the value')

Scroll in batches of say 1000:
create bulk delete requests and execute;
repeat until the end

This used to work no problem.

But now giving apparently random DocumentMissingException

Can't think why this might happen.

The mappings have been added to over time. Would that matter? I have heard
of the need to re-index.

I'm not even sure if the DocumentMissingException meant that the document
was there initially.

It could be a bug in the code. But it's single threaded and I can't see
how, if the document was there during the scan it's not there at the delete?

Anybody suggest what might be happening?

Obvious workaround is to simply ignore DocumentMissingException on delete
.. but why

Thanks.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d94413ef-bc1e-4879-a607-62ca1f802203%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.