I have an instance of Kibana that I am trying to connect to a Elasticsearch cluster. The Kibana server has a non-master and non-data instance of Elasticsearch configured as connected to the cluster. Here is the output of my ES cluster health:
"cluster_name" : "Elasticsearch-Cluster-1",
"status" : "green",
"timed_out" : false,
"number_of_nodes" : 4,
"number_of_data_nodes" : 3,
"active_primary_shards" : 2,
"active_shards" : 4,
"relocating_shards" : 0,
"initializing_shards" : 0,
"unassigned_shards" : 0,
"delayed_unassigned_shards" : 0,
"number_of_pending_tasks" : 0,
"number_of_in_flight_fetch" : 0,
"task_max_waiting_in_queue_millis" : 0,
"active_shards_percent_as_number" : 100.0
As you can see there are 4 nodes, only 3 of them are data nodes. The fourth is my Kibana server, so it is connecting to the cluster just fine. In all four nodes of the ES configuration I have bind address setup as:
network.host: _non_loopback:ipv4_
In the Kibana configuration I have elasticsearch.url setup as the IP of my Kibana server:
elasticsearch.url: "http://10.10.100.65:9200"
Prior to changing the above setting to what you see I was getting an error saying "Unable to connect to http://localhost:9200". Now the error just says plugin:elasticsearch Service Unavailable
Its not a firewall issue as all 4 node in the cluster have 9200/TCP and 9300/TCP open. I have confirmed this with an NMAP scan.
Anyone have any thoughts?