final request when scroll-scanning has 0 successful shards

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

final request when scroll-scanning has 0 successful shards

Tim S

When scroll-scanning, I keep scrolling until I get a result that returns 0 docs, which is what the docs seem to suggest that I should do.

But the final request (the one that returns 0 docs), always has _shards.successful=0. Normally, I’d consider this to indicate a failure (no shards responded). If doing a normal (non-scan) scroll, _shards.successful=1 (I’ve got 1 shard in this case), even when I’ve got to the point where there’s no more docs to scroll.

Is this a bug in the scanning? Or am I wrong to consider the _shards.successful=0 to indicate a failure?

Tested on version 1.3.1.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3998b393-476d-4fc4-a809-a15da19bdf8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: final request when scroll-scanning has 0 successful shards

Clinton Gormley-2
This is correct. On the last request, no hits are returned because all shards have already been drained of results.  If you look at shards.total and shards.failed, you'll see they are also 0

clint


On 4 August 2014 12:54, Tim S <[hidden email]> wrote:

When scroll-scanning, I keep scrolling until I get a result that returns 0 docs, which is what the docs seem to suggest that I should do.

But the final request (the one that returns 0 docs), always has _shards.successful=0. Normally, I’d consider this to indicate a failure (no shards responded). If doing a normal (non-scan) scroll, _shards.successful=1 (I’ve got 1 shard in this case), even when I’ve got to the point where there’s no more docs to scroll.

Is this a bug in the scanning? Or am I wrong to consider the _shards.successful=0 to indicate a failure?

Tested on version 1.3.1.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3998b393-476d-4fc4-a809-a15da19bdf8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAPt3XKQLaJAVtwvOgScGhr-inoT8KpG9k3_Q%2BpCvNetX%3DcpMNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: final request when scroll-scanning has 0 successful shards

Tim S
Yes, it makes sense in this case, it's just confusing because it happens differently in other situations - when doing a normal scroll (not scanning), shards.successful is non-zero even when you've reached the point where there's no more results (and even if you keep going). And if you do a search returning no results, shards.successful is also non-zero.

So, should I ever (not just when scrolling) consider shards.successful=0 to indicate a failure? Or should I ignore it and only look at the shards.failed?

On Monday, August 4, 2014 12:27:22 PM UTC+1, Clinton Gormley wrote:
This is correct. On the last request, no hits are returned because all shards have already been drained of results.  If you look at shards.total and shards.failed, you'll see they are also 0

clint


On 4 August 2014 12:54, Tim S <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="t3tvbgzItKgJ" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">tims...@...> wrote:

When <a href="http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/search-request-scroll.html#scroll-scan" target="_blank" onmousedown="this.href='http://www.google.com/url?q\75http%3A%2F%2Fwww.elasticsearch.org%2Fguide%2Fen%2Felasticsearch%2Freference%2F1.x%2Fsearch-request-scroll.html%23scroll-scan\46sa\75D\46sntz\0751\46usg\75AFQjCNEGnTFENIoiA_5lfkme3Adu220NCg';return true;" onclick="this.href='http://www.google.com/url?q\75http%3A%2F%2Fwww.elasticsearch.org%2Fguide%2Fen%2Felasticsearch%2Freference%2F1.x%2Fsearch-request-scroll.html%23scroll-scan\46sa\75D\46sntz\0751\46usg\75AFQjCNEGnTFENIoiA_5lfkme3Adu220NCg';return true;">scroll-scanning, I keep scrolling until I get a result that returns 0 docs, which is what the docs seem to suggest that I should do.

But the final request (the one that returns 0 docs), always has _shards.successful=0. Normally, I’d consider this to indicate a failure (no shards responded). If doing a normal (non-scan) scroll, _shards.successful=1 (I’ve got 1 shard in this case), even when I’ve got to the point where there’s no more docs to scroll.

Is this a bug in the scanning? Or am I wrong to consider the _shards.successful=0 to indicate a failure?

Tested on version 1.3.1.

--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="t3tvbgzItKgJ" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">elasticsearc...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/elasticsearch/3998b393-476d-4fc4-a809-a15da19bdf8d%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" onmousedown="this.href='https://groups.google.com/d/msgid/elasticsearch/3998b393-476d-4fc4-a809-a15da19bdf8d%40googlegroups.com?utm_medium\75email\46utm_source\75footer';return true;" onclick="this.href='https://groups.google.com/d/msgid/elasticsearch/3998b393-476d-4fc4-a809-a15da19bdf8d%40googlegroups.com?utm_medium\75email\46utm_source\75footer';return true;">https://groups.google.com/d/msgid/elasticsearch/3998b393-476d-4fc4-a809-a15da19bdf8d%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" onmousedown="this.href='https://groups.google.com/d/optout';return true;" onclick="this.href='https://groups.google.com/d/optout';return true;">https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/03dc5c45-01e3-4d1e-a23c-830a26ef4f3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.