X-Pack error on Node Failure


(Gayathri TR) #1

Hi Team,

We have 3 Elasticsearch Master nodes: Node_ELK_1,Node_ELK_2 and Node_ELK_3 and 2 slave nodes Node_ELK_4 and Node_ELK_5

X-Pack is enbaled on all servers for monitoring purpose.
We have configured the master nodes in such way that if one of them fails it will not effect the whole application by setting :

discovery.zen.minimum_master_nodes: 2
gateway.recover_after_nodes: 1

But it's not happening on a node failure. It throws below X-Pack errors:

Kindly advise on how we can configure X-Pack as my requirement

[2017-12-18T23:59:53,700][INFO ][o.e.x.m.e.Exporters ] [Node_ELK_1] skipping exporter [default_local] as it isn't ready yet
[2017-12-18T23:59:53,700][ERROR][o.e.x.m.AgentService ] [Node_ELK_1] exception when exporting documents
org.elasticsearch.xpack.monitoring.exporter.ExportException: exporters are either not ready or faulty
at org.elasticsearch.xpack.monitoring.exporter.Exporters.export(Exporters.java:188) ~[x-pack-5.0.2.jar:5.0.2]
at org.elasticsearch.xpack.monitoring.AgentService$ExportingWorker.run(AgentService.java:208) [x-pack-5.0.2.jar:5.0.2]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_144]

Regards,
Gayathri T R


(system) #2

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