# \[SOLVED\] Upgrade elasticsearch 2.3.3 to 5.0.1 request too low

**URL:** https://discuss.elastic.co/t/solved-upgrade-elasticsearch-2-3-3-to-5-0-1-request-too-low/68166
**Category:** Elasticsearch
**Created:** [December 6, 2016, 11:56am UTC](https://discuss.elastic.co/t/solved-upgrade-elasticsearch-2-3-3-to-5-0-1-request-too-low/68166 "2016-12-06T11:56:26Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![axelfelix](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@axelfelix](https://discuss.elastic.co/u/axelfelix)
#### Post date: [December 6, 2016, 11:56am UTC](https://discuss.elastic.co/t/solved-upgrade-elasticsearch-2-3-3-to-5-0-1-request-too-low/68166/1 "2016-12-06T11:56:27Z")

</div>

Hi all,

Since I've upraged ELK from 2.3.3 to 5.0.1, when I make a search request in Kibana, it is very low.

I try to figure out why.

In my elasticsearch configuration, I have these inputs:

```
thread_pool:
    search:
        size: 13
        queue_size: 12000

```

When I try to see some old visualization I get this warning (there is a connection ? ):

> Courier Fetch: 140 of 620 shards failed.

If you have any advice regarding this performance issue, please let me know.

Regards,  
Alex

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [December 6, 2016, 6:34pm UTC](https://discuss.elastic.co/t/solved-upgrade-elasticsearch-2-3-3-to-5-0-1-request-too-low/68166/2 "2016-12-06T18:34:43Z")

</div>

Check your ES logs, it should state why the fetch faild.

> [@axelfelix](#):
>
> In my elasticsearch configuration, I have these inputs:

That is not a good idea.

---

<div class="post-metadata">

### Author: ![axelfelix](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@axelfelix](https://discuss.elastic.co/u/axelfelix)
#### Post date: [December 7, 2016, 6:06pm UTC](https://discuss.elastic.co/t/solved-upgrade-elasticsearch-2-3-3-to-5-0-1-request-too-low/68166/3 "2016-12-07T18:06:08Z")

</div>

Thanks for your answer.

> [@warkolm](#):
>
> That is not a good idea.

Can you explain why ?

Thanks,  
Alex

---

<div class="post-metadata">

### Author: ![trisport88](https://avatars.discourse-cdn.com/v4/letter/t/a183cd/32.png) [@trisport88](https://discuss.elastic.co/u/trisport88)
#### Post date: [December 7, 2016, 6:27pm UTC](https://discuss.elastic.co/t/solved-upgrade-elasticsearch-2-3-3-to-5-0-1-request-too-low/68166/4 "2016-12-07T18:27:29Z")

</div>

> [@axelfelix](#):
>
> Can you explain why ?

Glad you asked for clarification. 🕶

My experience so far is that tuning the configuration is a bit of a mystic art. I have not had much success trying to figure out how to improve the index performance ([ES5 Indexing performance (seems slow)](https://discuss.elastic.co/t/es5-indexing-performance-seems-slow/65084)).

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [December 7, 2016, 8:28pm UTC](https://discuss.elastic.co/t/solved-upgrade-elasticsearch-2-3-3-to-5-0-1-request-too-low/68166/5 "2016-12-07T20:28:12Z")

</div>

Threadpools are stored in memory, by dramatically increasing the size you risk OOM. Also 12K requests might take a while to process, what do your clients do in the meantime?

---

<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 4, 2017, 8:28pm UTC](https://discuss.elastic.co/t/solved-upgrade-elasticsearch-2-3-3-to-5-0-1-request-too-low/68166/6 "2017-01-04T20:28:17Z")

</div>

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