API behaviors on index alias which points to several indices


Say we have index1 and index2 which are associated with alias1. Index1 has data from 05/11/2020, and index2 has data from 5/12/2020. We start a _scroll request to alias1 with the time range for data from 5/12/2020.
Initially this will cause searching on all the indices associated with alias1, as per (https://github.com/elastic/elasticsearch/issues/510).
My question is, on the second scroll call with passing in the new scroll id, with the query again be send to index1 despite no results being found in the first scroll?



Query will be sent to both index1 and index2 in every scroll iteration. You can verify this by setting slow query log thresholds to 0ms.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.