# How does refresh thread pool relate with bulk and search requets?

**URL:** https://discuss.elastic.co/t/how-does-refresh-thread-pool-relate-with-bulk-and-search-requets/69636
**Category:** Elasticsearch
**Created:** [December 21, 2016, 6:02am UTC](https://discuss.elastic.co/t/how-does-refresh-thread-pool-relate-with-bulk-and-search-requets/69636 "2016-12-21T06:02:06Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![YuWatanabe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuwatanabe/32/13259_2.png) [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)
#### Post date: [December 21, 2016, 6:02am UTC](https://discuss.elastic.co/t/how-does-refresh-thread-pool-relate-with-bulk-and-search-requets/69636/1 "2016-12-21T06:02:06Z")

</div>

By reading the [doc](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-threadpool.html) , I am assuming that requests travel through between thread pools as below.

Bulk Requests , such as elasticsearch output from logstash

[http pipeline](https://www.elastic.co/guide/en/elasticsearch/reference/5.1/modules-http.html) -\> **bulk thread pool** -\> **filesystem cache**

Search Requests, such as kibana dashboard

[http pipeline](https://www.elastic.co/guide/en/elasticsearch/reference/5.1/modules-http.html) -\> **search thread pool** -\> **filesystem cache**

However, how does the **refresh thread pool** relates with bulk and search operations?

---

<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 18, 2017, 6:02am UTC](https://discuss.elastic.co/t/how-does-refresh-thread-pool-relate-with-bulk-and-search-requets/69636/2 "2017-01-18T06:02:31Z")

</div>

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