# Slow ingestion problem (v 6.2.3)

**URL:** <https://discuss.elastic.co/t/slow-ingestion-problem-v-6-2-3/136225>\
**Category:** Elasticsearch\
**Created:** [June 18, 2018, 12:43am UTC](https://discuss.elastic.co/t/slow-ingestion-problem-v-6-2-3/136225 "2018-06-18T00:43:24Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![klahnakoski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/klahnakoski/32/3679_2.png) [@klahnakoski](https://discuss.elastic.co/u/klahnakoski)\
**Post date:** [June 18, 2018, 2:50pm UTC](https://discuss.elastic.co/t/slow-ingestion-problem-v-6-2-3/136225/9 "2018-06-18T14:50:11Z")

</div>

The application layer is setting the document IDs; they do not conform to the optimum specs found in the docs, but that can not be changed because there are (rare) cases when documents must be replaced.

The "backup nodes" are in a separate zone, and have a copy of all shards. There is only 2 right now, and they are not meant to accept queries. More here: [Moving shards is slow](https://discuss.elastic.co/t/moving-shards-is-slow/127363/9)

---

_[View the full topic](https://discuss.elastic.co/t/slow-ingestion-problem-v-6-2-3/136225)._