Remove http_addresses from Remote Cluster Info API #29207
Assignees
Labels
Comments
|
Pinging @elastic/es-core-infra |
|
@nik9000 Can you investigate this one and if appropriate, make the necessary changes? |
I'll take it! |
nik9000
added a commit
to nik9000/elasticsearch
that referenced
this issue
Apr 17, 2018
They are expensive to fetch and no longer needed by Kibana so they *shouldn't* be needed by anyone else either. Closes elastic#29207
nik9000
added a commit
that referenced
this issue
Apr 27, 2018
They are expensive to fetch and no longer needed by Kibana so they *shouldn't* be needed by anyone else either. Closes #29207
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently make node info API requests to remote clusters as part of the Remote Cluster Info API in order to return information about
http_addressesof the remote nodes.http_addresseswas originally introduced for kibana to do_field_capsbut this is not used in any actionable way and could be removed from the response or replaced with transport addresses, so that the the remote nodes info API calls can be skipped.Worth noting here that these API calls also require additional privileges for users running x-pack security.
The text was updated successfully, but these errors were encountered: