# Migration of Elasticsearch indices (58 GB) from 1.x to 2.x taking huge time

**URL:** <https://discuss.elastic.co/t/migration-of-elasticsearch-indices-58-gb-from-1-x-to-2-x-taking-huge-time/73210>\
**Category:** Elasticsearch\
**Created:** [January 30, 2017, 12:35pm UTC](https://discuss.elastic.co/t/migration-of-elasticsearch-indices-58-gb-from-1-x-to-2-x-taking-huge-time/73210 "2017-01-30T12:35:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![angshuman.ray](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/angshuman.ray/32/99106_2.png) [@angshuman.ray](https://discuss.elastic.co/u/angshuman.ray)\
**Post date:** [January 30, 2017, 12:35pm UTC](https://discuss.elastic.co/t/migration-of-elasticsearch-indices-58-gb-from-1-x-to-2-x-taking-huge-time/73210/1 "2017-01-30T12:35:13Z")

</div>

Hi,  
I need to migrate indices of 58 GB data from 1.x to 2.x Elasticsearch version but this migration is taking huge time, almost 2 days. It is not feasible for a production environment to shutdown for 2 days for data migration.

Please help me to find-out a way so that migration can be done as well as production system need not to keep shutdown.

Please validate my thinking below.

1. Continue with the migration from 1.x to 2.x with a separate instance of 2.x node.
2. Change the production system Elasticsearch to 2.x version (a separate node than step 1)
3. When the migration got completed then migrated Elsaticsearch 2.x node will be included in the production Elasticsearch cluster.

Regards,  
Angshuman

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [January 31, 2017, 9:35am UTC](https://discuss.elastic.co/t/migration-of-elasticsearch-indices-58-gb-from-1-x-to-2-x-taking-huge-time/73210/2 "2017-01-31T09:35:31Z")

</div>

Hey,

can you explain why the migration takes so long? What is the bottleneck? Getting the data out of elasticsearch? how are you reading the data from elasticsearch? please take some more time to properly explain your setup so others can help.

--Alex

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 31, 2017, 9:45am UTC](https://discuss.elastic.co/t/migration-of-elasticsearch-indices-58-gb-from-1-x-to-2-x-taking-huge-time/73210/3 "2017-01-31T09:45:19Z")

</div>

How are you migrating?

---

<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 28, 2017, 9:45am UTC](https://discuss.elastic.co/t/migration-of-elasticsearch-indices-58-gb-from-1-x-to-2-x-taking-huge-time/73210/4 "2017-02-28T09:45:20Z")

</div>

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