-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
Cross-cluster search remote cluster status API #23925
Comments
/cc @s1monw |
I chatted to @s1monw about how we should handle http vs https. Cross-cluster search will only work if all or none of the clusters are using TLS. Of course, it is possible that TLS is enabled on the transport layer but not on the HTTP layer. Outcome of the discussion is:
Also, instead of configuring HTTP addresses in the elasticsearch cluster state, we'll return a list of 3 addresses sniffed from the publish address in the nodes info of the remote cluster. If the clusters are set up with |
This commit adds an API to discover information like seed nodes, http addresses and connection status of a configured remote cluster. Closes elastic#23925
This commit adds an API to discover information like seed nodes, http addresses and connection status of a configured remote cluster. Closes #23925
This commit adds an API to discover information like seed nodes, http addresses and connection status of a configured remote cluster. Closes #23925
With cross-cluster search configured, Kibana needs to be able to:
http.publish_address
This is made more complicated by the fact that cluster settings can be
persistent
,transient
, ordefault
(configured in theelasticsearch.yml
file).Let's add a remote cluster status API like the following:
which could return something like:
The
http_addresses
could be pre-configured (see #23924) or be sniffed from the remote cluster's node info. (the same questions about HTTPS apply).The
level
key would indicate whether this remote cluster has been configured via the cluster settings or locally on the node.The text was updated successfully, but these errors were encountered: