Issue with cluster config

Elastic Stack Elasticsearch
1

i have 3 node with ES 5.2x & Kibana running, so when i try to cluster 2 nodes i am seeing below error in kibana logs and can't open Kibana UI, if i comment below line in elasticsearch.yml its fine, Any clue what could be the issue ?

#discovery.zen.ping.unicast.hosts: ["hostA","hostB"]

[$injector:unpr] Unknown provider: reportStatsProvider <- reportStats
AngularJS (http://localhost:5601/bundles/commons.bundle.js?v=14695:36)
Version: 5.2.0
Build: 14695
Error: Error: [$injector:unpr] Unknown provider: reportStatsProvider <- reportStats
AngularJS (http://localhost:5601/bundles/commons.bundle.js?v=14695:36)
onerror@http://localhost:5601/bundles/commons.bundle.js?v=14695:69:13512

2

That will never form a cluster as localhost can only ever be accessed locally. You may need to put in the actual IP.

3

Mark, i replaced ip with localhost when i posted my question sorry for any confusion, here is my Nodes config

NodeA
cluster.name: support-dev
node.name: sd-1
path.data: /apps/data/esdata/data/
path.logs: /apps/data/esdata/logs/
node.master: true
node.data: true
bootstrap.memory_lock: true
network.host: hostA
network.bind_host: 0.0.0.0
network.publish_host: hostA
discovery.zen.ping.unicast.hosts: ["hostA","hostB"]
discovery.zen.minimum_master_nodes: 2
xpack.security.enabled: false
xpack.monitoring.enabled: true
xpack.graph.enabled: false
xpack.watcher.enabled: false

NodeB
cluster.name: support-dev
node.name: sd-2
path.data: /apps/data/esdata/data/
path.logs: /apps/data/esdata/logs/
node.master: true
node.data: true
bootstrap.memory_lock: true
network.host: hostB
network.bind_host: 0.0.0.0
network.publish_host: hostB
discovery.zen.ping.unicast.hosts: ["hostA","hostB"]
discovery.zen.minimum_master_nodes: 2
xpack.security.enabled: false
xpack.monitoring.enabled: true
xpack.graph.enabled: false
xpack.watcher.enabled: false

I tried to get the cluster state with

curl -XGET 'http://hostA:9200/_cluster/state?pretty'

and here is the output

{
"error" : {
"root_cause" : [
{
"type" : "master_not_discovered_exception",
"reason" : null
}
],
"type" : "master_not_discovered_exception",
"reason" : null
},
"status" : 503
}

also i see below in the hostA logs

017-02-12T15:51:51,730][INFO ][o.e.d.z.ZenDiscovery ]
[sp-1] failed to send join request to master [{sp-2}{10_pnjCZTZSGVQYY-E0xWQ}{JFMvqYPATTi6X1loAqjwoQ}
{hostB}{ip2:9300}],
reason [RemoteTransportException[[sp-2][ip2:9300][internal:discovery/zen/join]];
nested: ConnectTransportException[[sp-1][ip1:9300] connect_timeout[30s]];

do you see any issues with above configs

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.