# Reindexing with sliced scrolls VS. using custom ranges **URL:** \ **Category:** Elasticsearch\ **Created:** [December 14, 2016, 10:22am UTC](https://discuss.elastic.co/t/reindexing-with-sliced-scrolls-vs-using-custom-ranges/69002 "2016-12-14T10:22:32Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![hariso](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hariso/32/50668_2.png) [@hariso](https://discuss.elastic.co/u/hariso)\ **Post date:** [December 14, 2016, 10:22am UTC](https://discuss.elastic.co/t/reindexing-with-sliced-scrolls-vs-using-custom-ranges/69002/1 "2016-12-14T10:22:32Z")
Hi guys! I'm reindexing a lot of data. To beef up the performance and also have more "elastic" error-handling, I've divided every source index into parts (ranges for a field). I then parallelize the process, by reindexing a number of ranges at a time. This has also the benefit of ranges being isolated, and so, if a range fails, I can investigate it and restart. In Elasticsearch 5.1 we have reindexing with sliced scrolls. I have two questions: 1. How does slicing compare with the approach above (manually specifying ranges) in terms of **performance**? 2. How does slicing compare with the approach above (manually specifying ranges) in terms of **error-handling**? i.e. if there is a problem with a single slice, can I simply restart it, with the rest of documents still being reindexed? Thanks in advance! Haris ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 11, 2017, 10:22am UTC](https://discuss.elastic.co/t/reindexing-with-sliced-scrolls-vs-using-custom-ranges/69002/2 "2017-01-11T10:22:38Z")
Closed on January 11, 2017, 10:22am UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.