# Kibana 6.1: Courier : searchSource segmented fetchSoon fetchNow

**URL:** <https://discuss.elastic.co/t/kibana-6-1-courier-searchsource-segmented-fetchsoon-fetchnow/200624>\
**Category:** Kibana\
**Created:** [September 23, 2019, 5:33am UTC](https://discuss.elastic.co/t/kibana-6-1-courier-searchsource-segmented-fetchsoon-fetchnow/200624 "2019-09-23T05:33:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![vvvprabhakar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vvvprabhakar/32/53806_2.png) [@vvvprabhakar](https://discuss.elastic.co/u/vvvprabhakar)\
**Post date:** [September 23, 2019, 5:33am UTC](https://discuss.elastic.co/t/kibana-6-1-courier-searchsource-segmented-fetchsoon-fetchnow/200624/1 "2019-09-23T05:33:28Z")

</div>

i want a clear understanding of all these things .

I am try to understand how kibana is fetching the logs from ES.

What is segmenting ? what is fetchsoon/fetchNow ? What is searchSource ?

How is courier architected ?

If some one can help

---

<div class="post-metadata">

**Author:** ![vvvprabhakar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vvvprabhakar/32/53806_2.png) [@vvvprabhakar](https://discuss.elastic.co/u/vvvprabhakar)\
**Post date:** [September 23, 2019, 7:15am UTC](https://discuss.elastic.co/t/kibana-6-1-courier-searchsource-segmented-fetchsoon-fetchnow/200624/2 "2019-09-23T07:15:46Z")

</div>

requestQueue  
getStartable  
fetchQueued

what are all these ?

---

<div class="post-metadata">

**Author:** ![vvvprabhakar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vvvprabhakar/32/53806_2.png) [@vvvprabhakar](https://discuss.elastic.co/u/vvvprabhakar)\
**Post date:** [September 25, 2019, 8:48am UTC](https://discuss.elastic.co/t/kibana-6-1-courier-searchsource-segmented-fetchsoon-fetchnow/200624/3 "2019-09-25T08:48:07Z")

</div>

@ [rashidkpc](https://github.com/rashidkpc) @rashidkpc

---

<div class="post-metadata">

**Author:** ![mikecote](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikecote/32/58549_2.png) [@mikecote](https://discuss.elastic.co/u/mikecote)\
**Post date:** [September 26, 2019, 3:20pm UTC](https://discuss.elastic.co/t/kibana-6-1-courier-searchsource-segmented-fetchsoon-fetchnow/200624/4 "2019-09-26T15:20:23Z")

</div>

Hi @vvvprabhakar,

The courier was designed to avoid sending too many requests to the server at the same time. Each browser has a maximum number of simultaneous connections allowed and Kibana would easily reach the limit causing requests to be queued in series.

The courier batches the requests together to solve this problem. Functions like below would be related to managing the queue:

fetchSoon: add the request to the queue  
fetchNow: bypass the queue  
getStartable: get a list of requests that can be sent  
fetchQueued: get result from getStartable and submit in a single request  
etc

Hope this helps,  
Mike.

---

<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:** [October 24, 2019, 3:20pm UTC](https://discuss.elastic.co/t/kibana-6-1-courier-searchsource-segmented-fetchsoon-fetchnow/200624/5 "2019-10-24T15:20:24Z")

</div>

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