# How to rescan existing objects metadata into New-Elastic?

**URL:** <https://discuss.elastic.co/t/how-to-rescan-existing-objects-metadata-into-new-elastic/180984>\
**Category:** Elasticsearch\
**Created:** [May 14, 2019, 10:50am UTC](https://discuss.elastic.co/t/how-to-rescan-existing-objects-metadata-into-new-elastic/180984 "2019-05-14T10:50:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![GuoSyuan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guosyuan/32/46149_2.png) [@GuoSyuan](https://discuss.elastic.co/u/GuoSyuan)\
**Post date:** [May 14, 2019, 10:50am UTC](https://discuss.elastic.co/t/how-to-rescan-existing-objects-metadata-into-new-elastic/180984/1 "2019-05-14T10:50:28Z")

</div>

Rebuild New-Elastic when elastic crash, How to rescan existing objects metadata into New-Elastic?

Any ideas?

---

<div class="post-metadata">

**Author:** ![GuoSyuan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guosyuan/32/46149_2.png) [@GuoSyuan](https://discuss.elastic.co/u/GuoSyuan)\
**Post date:** [May 22, 2019, 5:13am UTC](https://discuss.elastic.co/t/how-to-rescan-existing-objects-metadata-into-new-elastic/180984/2 "2019-05-22T05:13:09Z")

</div>

Hi All, We have found a way to touch objects as below.

The test scenario is ELK server crash or index not complete, and we can use the method for rescanning all object metadata per-bucket.

1. ELK no any index  

2. Rescan bucket objects  
**# aws s3 cp --metadata {"touched":"true"} s3://gstest02/ s3://gstest02/ --recursive --profile Taiwan-GS --endpoint-url [https://172.23.60.172:8082](https://172.23.60.172:8082) --ca-bundle /root/ca.pem**

3. The index back [Finish]  

share for all~

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [May 22, 2019, 5:31am UTC](https://discuss.elastic.co/t/how-to-rescan-existing-objects-metadata-into-new-elastic/180984/3 "2019-05-22T05:31:04Z")

</div>

Thanks for sharing your solution.  
Not sure exactly what it is though and basically what is running on `https://172.23.60.172:8082/`.

---

<div class="post-metadata">

**Author:** ![GuoSyuan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guosyuan/32/46149_2.png) [@GuoSyuan](https://discuss.elastic.co/u/GuoSyuan)\
**Post date:** [May 22, 2019, 6:31am UTC](https://discuss.elastic.co/t/how-to-rescan-existing-objects-metadata-into-new-elastic/180984/4 "2019-05-22T06:31:47Z")

</div>

The IP "172.23.60.172" is S3 compatible storage (note. It is NetApp StorageGRID )

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [May 22, 2019, 7:35am UTC](https://discuss.elastic.co/t/how-to-rescan-existing-objects-metadata-into-new-elastic/180984/5 "2019-05-22T07:35:11Z")

</div>

So I don't see how all this is connected to elasticsearch.

---

<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:** [June 19, 2019, 7:35am UTC](https://discuss.elastic.co/t/how-to-rescan-existing-objects-metadata-into-new-elastic/180984/6 "2019-06-19T07:35:28Z")

</div>

Closed on June 19, 2019, 7:35am UTC

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