Getting below errors while starting Elasticsearch

Elastic Stack Elasticsearch
1

Hi Team,

Getting below errors while starting Elasticsearch:

[2017-04-04T02:17:03,172][ERROR][o.e.x.m.c.c.ClusterStateCollector] [Node_1] collector [cluster-state-collector] timed out when collecting data
[2017-04-04T02:17:03,883][INFO ][o.e.m.j.JvmGcMonitorService] [Node_1] [gc][1279] overhead, spent [505ms] collecting in the last [1.1s]
[2017-04-04T02:17:15,941][INFO ][o.e.m.j.JvmGcMonitorService] [Node_1] [gc][1291] overhead, spent [480ms] collecting in the last [1s]
[2017-04-04T23:05:02,853][INFO ][o.e.x.w.w.WatchStore ] [Node_1] stopped watch store
[2017-04-04T23:05:10,116][ERROR][o.e.x.m.AgentService ] [Node_1] exception when exporting documents
org.elasticsearch.xpack.monitoring.exporter.ExportException: failed to flush export bulks
at org.elasticsearch.xpack.monitoring.exporter.ExportBulk$Compound.doFlush(ExportBulk.java:148) ~[x-pack-5.0.2.jar:5.0.2]
at org.elasticsearch.xpack.monitoring.exporter.ExportBulk.close(ExportBulk.java:77) ~[x-pack-5.0.2.jar:5.0.2]
at org.elasticsearch.xpack.monitoring.exporter.Exporters.export(Exporters.java:194) ~[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:745) [?:1.8.0_121]
Caused by: org.elasticsearch.xpack.monitoring.exporter.ExportException: failed to flush export bulk [default_local]
at org.elasticsearch.xpack.monitoring.exporter.local.LocalBulk.doFlush(LocalBulk.java:114) ~[?:?]
at org.elasticsearch.xpack.monitoring.exporter.ExportBulk.flush(ExportBulk.java:62) ~[?:?]
at org.elasticsearch.xpack.monitoring.exporter.ExportBulk$Compound.doFlush(ExportBulk.java:145) ~[?:?]
... 4 more

2

From the logs I assume that you're using ES 5.0.2? Is that right?
Also, what type of license for X-Pack do you have?

3

Hi,

yes, Iam using ES 5.0.2. I didn't install any licence for X-Pack

4

I assume this is a trial license then. That looks like an error from the monitoring feature of X-Pack. We did have a large number of fixes regarding skipped and timed out collection issues all the way up to 5.2.2.

5

Can You please share me the fixes....How to resolve the issues and make it up an running

6

There are a bunch of them and as X-Pack is not OSS, the best suggestion here would be to upgrade to a version >= 5.2.2.

7

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