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?
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
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?
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 <tims...@gmail.com <javascript:>> wrote:
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?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.