# Elasticsearch 2.3 bulk indexing performance

**URL:** <https://discuss.elastic.co/t/elasticsearch-2-3-bulk-indexing-performance/50899>\
**Category:** Elasticsearch\
**Created:** [May 25, 2016, 2:37am UTC](https://discuss.elastic.co/t/elasticsearch-2-3-bulk-indexing-performance/50899 "2016-05-25T02:37:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![yanjun](https://avatars.discourse-cdn.com/v4/letter/y/a6a055/32.png) [@yanjun](https://discuss.elastic.co/u/yanjun)\
**Post date:** [May 25, 2016, 2:37am UTC](https://discuss.elastic.co/t/elasticsearch-2-3-bulk-indexing-performance/50899/1 "2016-05-25T02:37:00Z")

</div>

I am testing out elasticsearch 2.3.3 performance and found out the index rate drops after a couple of hours (to a few hunder document/sec on each node). I have to restarted the cluster to bring the index rate back. Our setup is to have a client node accepting bulk request from logstash and sends out to a 40 data nodes cluster. They run on raid-0 spinning disks. I tried to watch the thread pool. There is always one node at a time to show bulk rejected value 5. Any insight how to improve the index performance?

---

<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 5, 2017, 10:49pm UTC](https://discuss.elastic.co/t/elasticsearch-2-3-bulk-indexing-performance/50899/2 "2017-07-05T22:49:18Z")

</div>