# Resuming Interrupted Reindexing Process
**URL:** https://discuss.elastic.co/t/resuming-interrupted-reindexing-process/18852
**Category:** Elasticsearch
**Created:** [July 24, 2014, 12:27am UTC](https://discuss.elastic.co/t/resuming-interrupted-reindexing-process/18852 "2014-07-24T00:27:58Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Sarang\_Zargar](https://discuss.elastic.co/u/Sarang_Zargar)
#### Post date: [July 24, 2014, 12:27am UTC](https://discuss.elastic.co/t/resuming-interrupted-reindexing-process/18852/1 "2014-07-24T00:27:58Z")
We are reindexing an index with following attributes:
- Size ~3TB
- Ever increasing (new records are pumped at high volume during peak
hours)
Is there a clean way to resume an interrupted reindexing process?
Does elastic search provides a way to persist the scrolls? If we can use
the same scroll we can essentially resume again.
What are the impacts of keeping scrolls alive for very long durations?
--
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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/dbb00ce5-535a-41d3-aea7-60d145a075f1%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/dbb00ce5-535a-41d3-aea7-60d145a075f1%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:13am UTC](https://discuss.elastic.co/t/resuming-interrupted-reindexing-process/18852/2 "2017-07-06T01:13:38Z")