Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use different queues for ES requests #97

Closed
To-om opened this issue Oct 25, 2020 · 1 comment
Closed

Use different queues for ES requests #97

To-om opened this issue Oct 25, 2020 · 1 comment
Assignees
@To-om
Milestone
1.11.6

Comments

@To-om
Copy link
Contributor

To-om commented Oct 25, 2020

Some operations requires many Elasticsearch requests. They saturate thread pool and connection pool and prevent all other operations to be executed before they are finished.
The aim of this issue is to use the thread pool (execution context) of the caller (not the global one) and create a dedicated connection pool of each one.
@To-om To-om self-assigned this Oct 25, 2020
@To-om To-om added this to the 1.11.6 milestone Oct 25, 2020
To-om added a commit that referenced this issue Oct 25, 2020
@To-om
#97 Use execution context from the caller
f3bc585
To-om added a commit that referenced this issue Oct 25, 2020
@To-om
#97 Use a dedicated connection pool (elastic client) for each executi…
3ba3aa2 
…on context
@To-om To-om closed this as completed Oct 26, 2020
To-om added a commit that referenced this issue Oct 26, 2020
@To-om
#97 Use execution context from the caller
bbac544
To-om added a commit that referenced this issue Oct 26, 2020
@To-om
#97 Use a dedicated connection pool (elastic client) for each executi…
e6ce84e 
…on context
@mback2k
Copy link

mback2k commented Apr 23, 2021 •
edited
Loading

@To-om I am sorry for hijacking this issue, but it seems like this is causing huge performance issues with Cortex version 3.0.1.

Since this seems to have been fixed on the es6 branch of elastic4play, I would like to kindly ask: would it be possible to get a new Cortex version for es6 released that contains these fixes (e.g. version 3.0.2)? I cannot migrate to es7 yet and spend a whole day debugging this issue, only to find out that the thread pooling is the root cause.

@mback2k mback2k mentioned this issue Jun 16, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@To-om To-om

Labels
None yet
Projects
None yet
Milestone
1.11.6
Development

No branches or pull requests
2 participants
@mback2k @To-om