# Reindex into another Elasticsearch

**URL:** <https://discuss.elastic.co/t/reindex-into-another-elasticsearch/23417>\
**Category:** Elasticsearch\
**Created:** [April 27, 2015, 11:50am UTC](https://discuss.elastic.co/t/reindex-into-another-elasticsearch/23417 "2015-04-27T11:50:49Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Frederico\_Ferreira](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frederico_ferreira/32/42268_2.png) [@Frederico\_Ferreira](https://discuss.elastic.co/u/Frederico_Ferreira)\
**Post date:** [April 27, 2015, 11:50am UTC](https://discuss.elastic.co/t/reindex-into-another-elasticsearch/23417/1 "2015-04-27T11:50:49Z")

</div>

This is my first e-mail, so, if this problem is already explained, i'm  
sorry, couldn't find out where it is.  
I'm out of ideas. This is my question:  
I had an Elasticsearch up and running with 1 replica, 5 shards, 1 master  
(data false) and 10 slaves, and every index configured by day (from  
logstash). Since we changed to a hourly index, after 2 weeks and a needed a  
maintenance reboot, Elasticsearch wasn't able to start properly. It started  
assigning unassigned shards and a lot of timeouts came to happen.

After 5 days trying to recover, we decided to change the configuration of  
our cluster to 1 master (data false), 10 salves and 1 shard 2 replicas  
indexes, from scratch, without any old index.  
My task now is to reindex those lost indexes. This is my problem:  
I have 10 backup files (up to 400gb each) and i'm looking for ways to  
reindex those indexes (little by little).

- Should i copy those indexes folder to the new cluster folder?
  - I don't need to change to a daily shard, i just need Elasticsearch  
to assign those indexes.

- Is there any way i'm able to differentiate replica folders from shards  
folders?

We're using Elasticsearch 1.4.4 and each Elasticsearch is in an 8-core,  
16gb ram dedicated machine.

--  
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/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS\_-0Q3Ey0Tw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS_-0Q3Ey0Tw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [April 27, 2015, 9:28pm UTC](https://discuss.elastic.co/t/reindex-into-another-elasticsearch/23417/2 "2015-04-27T21:28:28Z")

</div>

1 shard per index doesn't make a lot of sense unless you have very small  
amounts of data, You'd be better off going back to the default as you are  
solving the wrong problem there.

What are these backup file you mention, how did you get them out of ES?

On 27 April 2015 at 21:50, Frederico Ferreira [fredericobf@gmail.com](mailto:fredericobf@gmail.com) wrote:

> This is my first e-mail, so, if this problem is already explained, i'm  
> sorry, couldn't find out where it is.  
> I'm out of ideas. This is my question:  
> I had an Elasticsearch up and running with 1 replica, 5 shards, 1 master  
> (data false) and 10 slaves, and every index configured by day (from  
> logstash). Since we changed to a hourly index, after 2 weeks and a needed a  
> maintenance reboot, Elasticsearch wasn't able to start properly. It started  
> assigning unassigned shards and a lot of timeouts came to happen.
> 
> After 5 days trying to recover, we decided to change the configuration of  
> our cluster to 1 master (data false), 10 salves and 1 shard 2 replicas  
> indexes, from scratch, without any old index.  
> My task now is to reindex those lost indexes. This is my problem:  
> I have 10 backup files (up to 400gb each) and i'm looking for ways to  
> reindex those indexes (little by little).
> 
> - Should i copy those indexes folder to the new cluster folder?
> - I don't need to change to a daily shard, i just need  
> Elasticsearch to assign those indexes.
> 
> - Is there any way i'm able to differentiate replica folders from  
> shards folders?
> 
> We're using Elasticsearch 1.4.4 and each Elasticsearch is in an 8-core,  
> 16gb ram dedicated machine.
> 
> --  
> 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/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS\_-0Q3Ey0Tw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS_-0Q3Ey0Tw%40mail.gmail.com)  
> [https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS\_-0Q3Ey0Tw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS_-0Q3Ey0Tw%40mail.gmail.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/CAEYi1X92zDgRK18wNak-Q%2BsJVP8C8%2BqQz70bvxu\_jG%2BPmbq9CQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X92zDgRK18wNak-Q%2BsJVP8C8%2BqQz70bvxu_jG%2BPmbq9CQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Frederico\_Ferreira](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/frederico_ferreira/32/42268_2.png) [@Frederico\_Ferreira](https://discuss.elastic.co/u/Frederico_Ferreira)\
**Post date:** [May 14, 2015, 11:49pm UTC](https://discuss.elastic.co/t/reindex-into-another-elasticsearch/23417/3 "2015-05-14T23:49:47Z")

</div>

I'm sorry for the long delay it took to answer.  
Every index is a folder inside the data folder. I just simply compressed  
those folders and sent to S3.  
But, now, we just found an "answer":

- we built (at another dc) another ES cluster and we've put those  
folders inside the data directory
- this is the part that i didn't participate:
  - we had a Logstash querying ES and outputting to our ES cluster

- That's our answer to what we were looking for

Att  
Frederico Ferreira  
(21) 98714-1445

2015-04-27 18:28 GMT-03:00 Mark Walkom [markwalkom@gmail.com](mailto:markwalkom@gmail.com):

> 1 shard per index doesn't make a lot of sense unless you have very small  
> amounts of data, You'd be better off going back to the default as you are  
> solving the wrong problem there.
> 
> What are these backup file you mention, how did you get them out of ES?
> 
> On 27 April 2015 at 21:50, Frederico Ferreira [fredericobf@gmail.com](mailto:fredericobf@gmail.com)  
> wrote:
> 
> > This is my first e-mail, so, if this problem is already explained, i'm  
> > sorry, couldn't find out where it is.  
> > I'm out of ideas. This is my question:  
> > I had an Elasticsearch up and running with 1 replica, 5 shards, 1 master  
> > (data false) and 10 slaves, and every index configured by day (from  
> > logstash). Since we changed to a hourly index, after 2 weeks and a needed a  
> > maintenance reboot, Elasticsearch wasn't able to start properly. It started  
> > assigning unassigned shards and a lot of timeouts came to happen.
> > 
> > After 5 days trying to recover, we decided to change the configuration of  
> > our cluster to 1 master (data false), 10 salves and 1 shard 2 replicas  
> > indexes, from scratch, without any old index.  
> > My task now is to reindex those lost indexes. This is my problem:  
> > I have 10 backup files (up to 400gb each) and i'm looking for ways to  
> > reindex those indexes (little by little).
> > 
> > - Should i copy those indexes folder to the new cluster folder?
> > - I don't need to change to a daily shard, i just need  
> > Elasticsearch to assign those indexes.
> > 
> > - Is there any way i'm able to differentiate replica folders from  
> > shards folders?
> > 
> > We're using Elasticsearch 1.4.4 and each Elasticsearch is in an 8-core,  
> > 16gb ram dedicated machine.
> > 
> > --  
> > 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/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS\_-0Q3Ey0Tw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS_-0Q3Ey0Tw%40mail.gmail.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS\_-0Q3Ey0Tw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS_-0Q3Ey0Tw%40mail.gmail.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> 
> --  
> 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/CAEYi1X92zDgRK18wNak-Q%2BsJVP8C8%2BqQz70bvxu\_jG%2BPmbq9CQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X92zDgRK18wNak-Q%2BsJVP8C8%2BqQz70bvxu_jG%2BPmbq9CQ%40mail.gmail.com)  
> [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X92zDgRK18wNak-Q%2BsJVP8C8%2BqQz70bvxu\_jG%2BPmbq9CQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X92zDgRK18wNak-Q%2BsJVP8C8%2BqQz70bvxu_jG%2BPmbq9CQ%40mail.gmail.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/)

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/CAM0Xh3i2FzNpBdrtqV6MOOqUSMd7x-FEi\_ZEgA38V1CZOnJBpw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3i2FzNpBdrtqV6MOOqUSMd7x-FEi_ZEgA38V1CZOnJBpw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [May 15, 2015, 2:00am UTC](https://discuss.elastic.co/t/reindex-into-another-elasticsearch/23417/4 "2015-05-15T02:00:31Z")

</div>

You're better off using the snapshot and restore functionality than doing  
your method.

I'm not sure what you are trying to do though

On 15 May 2015 at 09:49, Frederico Ferreira [fredericobf@gmail.com](mailto:fredericobf@gmail.com) wrote:

> I'm sorry for the long delay it took to answer.  
> Every index is a folder inside the data folder. I just simply compressed  
> those folders and sent to S3.  
> But, now, we just found an "answer":
> 
> - we built (at another dc) another ES cluster and we've put those  
> folders inside the data directory
> - this is the part that i didn't participate:
> - we had a Logstash querying ES and outputting to our ES cluster
> 
> - That's our answer to what we were looking for
> 
> Att  
> Frederico Ferreira  
> (21) 98714-1445
> 
> 2015-04-27 18:28 GMT-03:00 Mark Walkom [markwalkom@gmail.com](mailto:markwalkom@gmail.com):
> 
> > 1 shard per index doesn't make a lot of sense unless you have very small  
> > amounts of data, You'd be better off going back to the default as you are  
> > solving the wrong problem there.
> > 
> > What are these backup file you mention, how did you get them out of ES?
> > 
> > On 27 April 2015 at 21:50, Frederico Ferreira [fredericobf@gmail.com](mailto:fredericobf@gmail.com)  
> > wrote:
> > 
> > > This is my first e-mail, so, if this problem is already explained, i'm  
> > > sorry, couldn't find out where it is.  
> > > I'm out of ideas. This is my question:  
> > > I had an Elasticsearch up and running with 1 replica, 5 shards, 1 master  
> > > (data false) and 10 slaves, and every index configured by day (from  
> > > logstash). Since we changed to a hourly index, after 2 weeks and a needed a  
> > > maintenance reboot, Elasticsearch wasn't able to start properly. It started  
> > > assigning unassigned shards and a lot of timeouts came to happen.
> > > 
> > > After 5 days trying to recover, we decided to change the configuration  
> > > of our cluster to 1 master (data false), 10 salves and 1 shard 2 replicas  
> > > indexes, from scratch, without any old index.  
> > > My task now is to reindex those lost indexes. This is my problem:  
> > > I have 10 backup files (up to 400gb each) and i'm looking for ways to  
> > > reindex those indexes (little by little).
> > > 
> > > - Should i copy those indexes folder to the new cluster folder?
> > > - I don't need to change to a daily shard, i just need  
> > > Elasticsearch to assign those indexes.
> > > 
> > > - Is there any way i'm able to differentiate replica folders from  
> > > shards folders?
> > > 
> > > We're using Elasticsearch 1.4.4 and each Elasticsearch is in an 8-core,  
> > > 16gb ram dedicated machine.
> > > 
> > > --  
> > > 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/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS\_-0Q3Ey0Tw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS_-0Q3Ey0Tw%40mail.gmail.com)  
> > > [https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS\_-0Q3Ey0Tw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS_-0Q3Ey0Tw%40mail.gmail.com?utm_medium=email&utm_source=footer)  
> > > .  
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> > 
> > --  
> > 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/CAEYi1X92zDgRK18wNak-Q%2BsJVP8C8%2BqQz70bvxu\_jG%2BPmbq9CQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X92zDgRK18wNak-Q%2BsJVP8C8%2BqQz70bvxu_jG%2BPmbq9CQ%40mail.gmail.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X92zDgRK18wNak-Q%2BsJVP8C8%2BqQz70bvxu\_jG%2BPmbq9CQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X92zDgRK18wNak-Q%2BsJVP8C8%2BqQz70bvxu_jG%2BPmbq9CQ%40mail.gmail.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> 
> ## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/)
> 
> 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/CAM0Xh3i2FzNpBdrtqV6MOOqUSMd7x-FEi\_ZEgA38V1CZOnJBpw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3i2FzNpBdrtqV6MOOqUSMd7x-FEi_ZEgA38V1CZOnJBpw%40mail.gmail.com)  
> [https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3i2FzNpBdrtqV6MOOqUSMd7x-FEi\_ZEgA38V1CZOnJBpw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3i2FzNpBdrtqV6MOOqUSMd7x-FEi_ZEgA38V1CZOnJBpw%40mail.gmail.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/)

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/CAEYi1X89JbL0T1GwoLct%3DS4uK6EPS\_EZLf538raqOH5pxq2ggQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X89JbL0T1GwoLct%3DS4uK6EPS_EZLf538raqOH5pxq2ggQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![bitsofinfo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bitsofinfo/32/459_2.png) [@bitsofinfo](https://discuss.elastic.co/u/bitsofinfo)\
**Post date:** [June 1, 2015, 2:31pm UTC](https://discuss.elastic.co/t/reindex-into-another-elasticsearch/23417/5 "2015-06-01T14:31:33Z")

</div>

Also try this tool for more easily aggregating FS repo snapshots across a  
cluster for restoring on a different cluster. I had to make this tool for a  
similar scenario I had, might help in your situation  
too [GitHub - bitsofinfo/elasticsearch-snapshot-manager: Scala tool for managing elasticsearch snapshots. In particular aggregating and backing up snapshots files from fs local-disk snapshot repositories distributed across a large cluster.](https://github.com/bitsofinfo/elasticsearch-snapshot-manager)

On Thursday, May 14, 2015 at 5:50:33 PM UTC-6, Frederico Barnard wrote:

> I'm sorry for the long delay it took to answer.  
> Every index is a folder inside the data folder. I just simply compressed  
> those folders and sent to S3.  
> But, now, we just found an "answer":
> 
> - we built (at another dc) another ES cluster and we've put those  
> folders inside the data directory
> - this is the part that i didn't participate:
> - we had a Logstash querying ES and outputting to our ES cluster
> 
> - That's our answer to what we were looking for
> 
> Att  
> Frederico Ferreira  
> (21) 98714-1445
> 
> 2015-04-27 18:28 GMT-03:00 Mark Walkom \<[markw...@gmail.com](mailto:markw...@gmail.com) \<javascript:\>\>:
> 
> > 1 shard per index doesn't make a lot of sense unless you have very small  
> > amounts of data, You'd be better off going back to the default as you are  
> > solving the wrong problem there.
> > 
> > What are these backup file you mention, how did you get them out of ES?
> > 
> > On 27 April 2015 at 21:50, Frederico Ferreira \<[frede...@gmail.com](mailto:frede...@gmail.com)  
> > \<javascript:\>\> wrote:
> > 
> > > This is my first e-mail, so, if this problem is already explained, i'm  
> > > sorry, couldn't find out where it is.  
> > > I'm out of ideas. This is my question:  
> > > I had an Elasticsearch up and running with 1 replica, 5 shards, 1 master  
> > > (data false) and 10 slaves, and every index configured by day (from  
> > > logstash). Since we changed to a hourly index, after 2 weeks and a needed a  
> > > maintenance reboot, Elasticsearch wasn't able to start properly. It started  
> > > assigning unassigned shards and a lot of timeouts came to happen.
> > > 
> > > After 5 days trying to recover, we decided to change the configuration  
> > > of our cluster to 1 master (data false), 10 salves and 1 shard 2 replicas  
> > > indexes, from scratch, without any old index.  
> > > My task now is to reindex those lost indexes. This is my problem:  
> > > I have 10 backup files (up to 400gb each) and i'm looking for ways to  
> > > reindex those indexes (little by little).
> > > 
> > > - Should i copy those indexes folder to the new cluster folder?
> > > - I don't need to change to a daily shard, i just need  
> > > Elasticsearch to assign those indexes.
> > > 
> > > - Is there any way i'm able to differentiate replica folders from  
> > > shards folders?
> > > 
> > > We're using Elasticsearch 1.4.4 and each Elasticsearch is in an 8-core,  
> > > 16gb ram dedicated machine.
> > > 
> > > --  
> > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > > To view this discussion on the web visit  
> > > [https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS\_-0Q3Ey0Tw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS_-0Q3Ey0Tw%40mail.gmail.com)  
> > > [https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS\_-0Q3Ey0Tw%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAM0Xh3hG7BfiTwDgc0cCseTg4dVNFvav6LWvOmHS_-0Q3Ey0Tw%40mail.gmail.com?utm_medium=email&utm_source=footer)  
> > > .  
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> > 
> > --  
> > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X92zDgRK18wNak-Q%2BsJVP8C8%2BqQz70bvxu\_jG%2BPmbq9CQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X92zDgRK18wNak-Q%2BsJVP8C8%2BqQz70bvxu_jG%2BPmbq9CQ%40mail.gmail.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X92zDgRK18wNak-Q%2BsJVP8C8%2BqQz70bvxu\_jG%2BPmbq9CQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X92zDgRK18wNak-Q%2BsJVP8C8%2BqQz70bvxu_jG%2BPmbq9CQ%40mail.gmail.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/)

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/4c6feaec-276d-4fc2-8600-244acd1d1571%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4c6feaec-276d-4fc2-8600-244acd1d1571%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [July 6, 2017, 12:10am UTC](https://discuss.elastic.co/t/reindex-into-another-elasticsearch/23417/6 "2017-07-06T00:10:27Z")

</div>


