Waiting for elected master node to setup local exporter [default_local] (does it have x-pack installed?)

Hi,
I have a cluster of two elasticsearch instances.
After the update from 6.3.1 to 6.4 the elasticsearch log on one machine is flooded with messages like the following:

[2018-08-29T13:17:01,091][INFO ][o.e.x.m.e.l.LocalExporter] waiting for elected master node [{Grace Hopper}{NKo4EY3cSeWn4lhgMJdrIg}{pjWhPYUcS1WI4k7CZbmj3A}{192.168.96.172}{192.168.96.172:9300}{ml.machine_memory=12411981824, ml.max_open_jobs=20, xpack.installed=true, ml.enabled=true}] to setup local exporter [default_local] (does it have x-pack installed?)

The elasticsearch log on the other machine is flooded with:

[2018-08-29T13:20:54,717][ERROR][o.e.x.m.e.l.LocalExporter] failed to set monitoring pipeline [xpack_monitoring_2]
org.elasticsearch.cluster.metadata.ProcessClusterEventTimeoutException: failed to process cluster event (put-pipeline-xpack_monitoring_2) within 30s
at org.elasticsearch.cluster.service.MasterService$Batcher.lambda$onTimeout$0(MasterService.java:125) ~[elasticsearch-6.4.0.jar:6.4.0]
at java.util.ArrayList.forEach(ArrayList.java:1257) ~[?:1.8.0_181]
at org.elasticsearch.cluster.service.MasterService$Batcher.lambda$onTimeout$1(MasterService.java:124) ~[elasticsearch-6.4.0.jar:6.4.0]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:624) [elasticsearch-6.4.0.jar:6.4.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_181]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_181]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]

How do I solve this?

Best regards,
Robert

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