Skip to content

Low level REST client marks arbitrary node as dead when the connection pool is exhausted #40925

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

Closed
amirhadadi opened this issue Apr 6, 2019 · 2 comments
Labels
:Clients/Java Low Level REST Client Minimal dependencies Java Client for Elasticsearch Team:Data Management Meta label for data/management team

Comments

@amirhadadi
Copy link

Elasticsearch version 6.3.2

Plugins installed: []

JVM version: 1.8.144

OS version: Linux 3.13.0-88-generic #135-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

When HttpAsyncClientBuilder::maxConnTotal is exceeded, a leasing request is placed for a connection by AbstractNIOConnPool with a deadline derived from HttpAsyncClientBuilder::connectionRequestTimeout. If the deadline is reached, a TimeoutException is propagated to the REST client reaching the failed(Exception failure) callback in RestClient::performRequestAsync which marks the node as dead.
However, the failure is a result of the connection pool in its entirety being exhausted and not the node itself having any issue.

@amirhadadi amirhadadi changed the title REST client marks arbitrary node as dead when the connection pool is exhausted Low level REST client marks arbitrary node as dead when the connection pool is exhausted Apr 6, 2019
@dnhatn dnhatn added the :Clients/Java Low Level REST Client Minimal dependencies Java Client for Elasticsearch label Apr 6, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

@rjernst rjernst added the Team:Data Management Meta label for data/management team label May 4, 2020
@dakrone
Copy link
Member

dakrone commented May 17, 2024

This has been open for quite a while, and we haven't made much progress on this due to focus in other areas. For now I'm going to close this as something we aren't planning on implementing. We can re-open it later if needed.

@dakrone dakrone closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Clients/Java Low Level REST Client Minimal dependencies Java Client for Elasticsearch Team:Data Management Meta label for data/management team
Projects
None yet
Development

No branches or pull requests

5 participants