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
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
requestQueue
getStartable
fetchQueued
what are all these ?
@ rashidkpc @rashidkpc
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.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.