You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
apiman/common/es/src/main/java/io/apiman/common/es/util/DefaultEsClientFactory.java
Line 105 in 347f4a8
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
The text was updated successfully, but these errors were encountered: