# Concurrent bulk requests

**URL:** <https://discuss.elastic.co/t/concurrent-bulk-requests/128140>\
**Category:** Elasticsearch\
**Created:** [April 16, 2018, 8:53am UTC](https://discuss.elastic.co/t/concurrent-bulk-requests/128140 "2018-04-16T08:53:23Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![kchrusciel](https://avatars.discourse-cdn.com/v4/letter/k/53a042/32.png) [@kchrusciel](https://discuss.elastic.co/u/kchrusciel)\
**Post date:** [April 16, 2018, 8:53am UTC](https://discuss.elastic.co/t/concurrent-bulk-requests/128140/1 "2018-04-16T08:53:23Z")

</div>

Hi,

I do concurrent bulk requests (inserting) in 20 threads. When I look at threads all of them waiting in:

 ![jobs](https://us1.discourse-cdn.com/elastic/original/3X/a/7/a757f3d3d6dd81bac3975af20f567d9bab1d6724.png)

![job](https://us1.discourse-cdn.com/elastic/original/3X/9/c/9c15a6ee8ee44356828e5ca697f2abf376084e4d.png)

Can I somehow speedup this process?

---

<div class="post-metadata">

**Author:** ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)\
**Post date:** [April 16, 2018, 7:48pm UTC](https://discuss.elastic.co/t/concurrent-bulk-requests/128140/2 "2018-04-16T19:48:02Z")

</div>

How did you get this report? (just curious).

---

<div class="post-metadata">

**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\
**Post date:** [April 17, 2018, 2:17am UTC](https://discuss.elastic.co/t/concurrent-bulk-requests/128140/3 "2018-04-17T02:17:34Z")

</div>

That does not look like the name of bulk threads used in Elasticsearch.

---

<div class="post-metadata">

**Author:** ![kchrusciel](https://avatars.discourse-cdn.com/v4/letter/k/53a042/32.png) [@kchrusciel](https://discuss.elastic.co/u/kchrusciel)\
**Post date:** [April 17, 2018, 5:43am UTC](https://discuss.elastic.co/t/concurrent-bulk-requests/128140/4 "2018-04-17T05:43:46Z")

</div>

I named my threads which are responsible for bulk requests.

But, all of them are in WAITING state in  
`org.elasticsearch.common,util.concurrent.BaseFuture$Sync.get`

Of course, finally the requests are done without any exception, but to compare with an older version (1.7.1), the bulk process takes much more time in the newest version.

I run this tasks in 20 threads, I know that queue size for the bulk request is 200.

Do you know how to speed up this process (I do all steps from [https://www.elastic.co/guide/en/elasticsearch/reference/6.2/tune-for-indexing-speed.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/tune-for-indexing-speed.html))?

---

<div class="post-metadata">

**Author:** ![kchrusciel](https://avatars.discourse-cdn.com/v4/letter/k/53a042/32.png) [@kchrusciel](https://discuss.elastic.co/u/kchrusciel)\
**Post date:** [April 17, 2018, 5:45am UTC](https://discuss.elastic.co/t/concurrent-bulk-requests/128140/5 "2018-04-17T05:45:29Z")

</div>

I run my tasks in my own thread pull. I run VisualVM and I look on threads, why this indexing process takes too much time. I see that all of my bulk threads are in WAITING state, looks like problem with asynchronus tasks.

---

<div class="post-metadata">

**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\
**Post date:** [April 17, 2018, 1:04pm UTC](https://discuss.elastic.co/t/concurrent-bulk-requests/128140/6 "2018-04-17T13:04:53Z")

</div>

So this is client side then. These threads are waiting on a reply from the server. You need to see why the server is taking so long to reply, maybe you're overwhelming it.

---

<div class="post-metadata">

**Author:** ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)\
**Post date:** [April 18, 2018, 8:04am UTC](https://discuss.elastic.co/t/concurrent-bulk-requests/128140/7 "2018-04-18T08:04:44Z")

</div>

Ho, this is not from elasticsearch so?

Check the thread\_pool to see what thread are doing (/\_cat/thread\_pool?v&human)

If I am right, for indexing 1 thread can take care of 1 primary shard.

---

<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:** [May 16, 2018, 8:14am UTC](https://discuss.elastic.co/t/concurrent-bulk-requests/128140/8 "2018-05-16T08:14:22Z")

</div>

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