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

Support for specifying muliple elasticsearch hosts #2587

Open
cen1 opened this issue Aug 31, 2023 · 0 comments
Open

Support for specifying muliple elasticsearch hosts #2587

cen1 opened this issue Aug 31, 2023 · 0 comments

Comments

@cen1
Copy link

cen1 commented Aug 31, 2023

Apiman Version

master

Apiman Manager Distro

WildFly

Apiman Gateway Distro

WildFly

Java Version

11

Operating System

Centos 8

Are you running Apiman in a container, or on an orchestration platform?

No (Bare Metal)

Describe the bug

It seems that it is not possible to specify multiple ES hosts when running against a proper multi node production ES cluster.

A look into the code also reveals that a single host is used:

RestClientBuilder clientBuilder = RestClient.builder(new HttpHost(host, port, protocol))
even though the builder can accept multiple.

Is this just an original sin that was overlooked when ES support was added? Is there a way to do it that I missed?

I saw some workarounds with keepalived thrown across the ES nodes but that is not a good solution, all ES libraries I have ever used accept an array and handle the proper selection internally.

Expected behaviour

No response

Actual behaviour

No response

How to Reproduce

No response

Relevant log output

No response

Anything else?

No response

@cen1 cen1 changed the title Support for spcifying muliple ES hosts Support for specifying muliple ES hosts Aug 31, 2023
@cen1 cen1 changed the title Support for specifying muliple ES hosts Support for specifying muliple elasticsearch hosts Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant