# Logstash or re-index API to chose for re-indexing?

**URL:** <https://discuss.elastic.co/t/logstash-or-re-index-api-to-chose-for-re-indexing/215435>\
**Category:** Logstash\
**Created:** [January 17, 2020, 10:18am UTC](https://discuss.elastic.co/t/logstash-or-re-index-api-to-chose-for-re-indexing/215435 "2020-01-17T10:18:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![arunpmohan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arunpmohan/32/69467_2.png) [@arunpmohan](https://discuss.elastic.co/u/arunpmohan)\
**Post date:** [January 17, 2020, 10:18am UTC](https://discuss.elastic.co/t/logstash-or-re-index-api-to-chose-for-re-indexing/215435/1 "2020-01-17T10:18:59Z")

</div>

We have a cluster with the following configurations

1. 12 nodes
2. Elasticsearch 5.x
3. 24 TB data

I need to upgrade this cluster to Elasticsearch 7.x  
So we have come up with a plan to provision a new cluster with exact same hardware configurations as that of the original.

We need to re-index the data from the 5.x to 7.x cluster.  
We are considering two options for that

1. using a single powerfull logstash machine
2. using the re-index API from the 7.x cluster

Which one is a better choice?  
Does the re-index API makes use of all nodes (all nodes are master eligible, ingest and data nodes by default) and fare better than a single logstash machine?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 14, 2020, 10:19am UTC](https://discuss.elastic.co/t/logstash-or-re-index-api-to-chose-for-re-indexing/215435/2 "2020-02-14T10:19:01Z")

</div>

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