# Build index problem when batch import

**URL:** <https://discuss.elastic.co/t/build-index-problem-when-batch-import/161234>\
**Category:** Elasticsearch\
**Created:** [December 18, 2018, 2:17am UTC](https://discuss.elastic.co/t/build-index-problem-when-batch-import/161234 "2018-12-18T02:17:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![zcx](https://avatars.discourse-cdn.com/v4/letter/z/e68b1a/32.png) [@zcx](https://discuss.elastic.co/u/zcx)\
**Post date:** [December 18, 2018, 2:17am UTC](https://discuss.elastic.co/t/build-index-problem-when-batch-import/161234/1 "2018-12-18T02:17:41Z")

</div>

If you're doing bulk imports, consider closing copies by setting index.number\_of\_replicas: 0.When a document is copied, the entire document content is sent to the replica node and the indexing process is repeated verbatim.This means that each copy also performs analysis, indexing, and possibly merging.

Conversely, if your index is a zero copy and you open the copy after the write is complete, the recovery process is essentially a byte to byte network transfer.This is quite efficient compared to repeating the indexing process.

Is this true?

---

<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:** [January 15, 2019, 2:17am UTC](https://discuss.elastic.co/t/build-index-problem-when-batch-import/161234/2 "2019-01-15T02:17:42Z")

</div>

Closed on January 15, 2019, 2:17am UTC

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