# Using my own document\_id - is there a faster way?

**URL:** <https://discuss.elastic.co/t/using-my-own-document-id-is-there-a-faster-way/108667>\
**Category:** Logstash\
**Created:** [November 22, 2017, 8:12am UTC](https://discuss.elastic.co/t/using-my-own-document-id-is-there-a-faster-way/108667 "2017-11-22T08:12:16Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![elastic\_paul](https://avatars.discourse-cdn.com/v4/letter/e/ebca7d/32.png) [@elastic\_paul](https://discuss.elastic.co/u/elastic_paul)\
**Post date:** [November 29, 2017, 6:24am UTC](https://discuss.elastic.co/t/using-my-own-document-id-is-there-a-faster-way/108667/26 "2017-11-29T06:24:54Z")

</div>

Over on a separate thread in [Elasticsearch](https://discuss.elastic.co/t/how-to-start-two-instances-of-es-6-0-as-a-service/109328/4) I discussed and implemented 2 instances per node in my cluster, along with many of the other changes discussed here.

I also changed my logstash configuration so that all data is sent to a single ES instance, and that instance can then pass the data within the cluster. Rather than flooding all 8 instances (2 per node) with data, which resulted in overloading everything.

Its all stable and loading in data in the 12,000-15,000/s range.  
Thanks for all of the help and guidance.

---

_[View the full topic](https://discuss.elastic.co/t/using-my-own-document-id-is-there-a-faster-way/108667)._