# SCAN Search type behavior explanation **URL:** \ **Category:** Elasticsearch\ **Created:** [January 14, 2013, 11:20pm UTC](https://discuss.elastic.co/t/scan-search-type-behavior-explanation/10339 "2013-01-14T23:20:00Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![y\_itay](https://avatars.discourse-cdn.com/v4/letter/y/76d3ee/32.png) [@y\_itay](https://discuss.elastic.co/u/y_itay)\ **Post date:** [January 14, 2013, 11:20pm UTC](https://discuss.elastic.co/t/scan-search-type-behavior-explanation/10339/1 "2013-01-14T23:20:00Z")
Hey, I'm working right now on a use-case where I need to index all my data. I read on elasticsearch forums that SCAN search type will be the best approach to do that. I have 2 questions regarding the SCAN/scroll: 1. I know each scroll has a time to live, I was wondering if after this time is elapsed and I scroll another page if the first scroll segments are removed if the documents from the first scan got updated. 2. Another requirement we have is to support sending multiple SCANs at the same time, is there any concern running 10-100 SCANs at the same time? any memory constraints I need to be aware besides the index size which might grow? Thanks for the help! -Itay -- ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:56am UTC](https://discuss.elastic.co/t/scan-search-type-behavior-explanation/10339/2 "2017-07-06T02:56:31Z")