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.

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

run response actionListener in SAME ThreadPool #2363

Merged
merged 1 commit into from
Jul 28, 2015

Conversation

mfussenegger
Copy link
Member

usually the onResponse operation is very cheap and can run on the IO/caller
thread directly.

If the response operation is expensive the listener should be wrapped into a
ThreadedActionListener or a different ResponseHandler should be used.

This avoids EsRejectedExecutionExceptions which can cause queries to get stuck
as the response could be swallowed.

@seut
Copy link
Member

seut commented Jul 28, 2015

ack

@chaudum
Copy link
Contributor

chaudum commented Jul 28, 2015

otherwise ack

usually the onResponse operation is very cheap and can run
on the IO/caller thread directly.

If the response operation is expensive the listener should
be wrapped into a ThreadedActionListener or a different
ResponseHandler should be used.

This avoids EsRejectedExecutionExceptions which can cause
queries to get stuck as the response could be swallowed.
@mfussenegger mfussenegger merged commit 6d07121 into rejected-execution Jul 28, 2015
@mfussenegger mfussenegger deleted the j/response-handler branch July 28, 2015 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants