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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/dbb00ce5-535a-41d3-aea7-60d145a075f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.