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

Location awareness in low level RestClient #28500

Closed
edudar opened this issue Feb 2, 2018 · 2 comments
Closed

Location awareness in low level RestClient #28500

edudar opened this issue Feb 2, 2018 · 2 comments
Labels
:Clients/Java Low Level REST Client Minimal dependencies Java Client for Elasticsearch

Comments

@edudar
Copy link

edudar commented Feb 2, 2018

Right now RestClient accepts a set of hosts it will rotate through doing client-side load balancing. When the server runs in AWS it's good practice to spread instances across multiple availability zones and to make requests within your availability zone preferably, falling back to out of zone requests when necessary. It would be good to have two sets of addresses RestClient rotates through. One is the primary set which can be filled with client/data nodes within your availability zone and the other one is secondary set where client/data nodes outside of your availability zone will reside. In this case, a client should rotate primary nodes (even if there's only one node) and fallback to secondary nodes when the primary is empty/blacklisted.

@javanna
Copy link
Member

javanna commented Feb 8, 2018

I believe this will be addressed by implementing a custom node selector once we have added support for them as part of #21888 .

@javanna
Copy link
Member

javanna commented Feb 12, 2018

Closing, will be implemented as part of #21888 like mentioned above.

@javanna javanna closed this as completed Feb 12, 2018
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
Projects
None yet
Development

No branches or pull requests

3 participants