Elasticsearch logs


(Raj) #1

Hi All,

I was trying to see the elasticsearch logs and I was able to find these type of logs are loading the server very fastly.

[2017-05-01T12:26:23,993][DEBUG][o.e.a.b.TransportBulkAction] [casa_1] failed to execute pipeline [xpack_monitoring_2] for document [.monitoring-data-2/logstash/37cd9d97-fcff-4042-925e-b2467af2b695]
java.lang.IllegalArgumentException: pipeline with id [xpack_monitoring_2] does not exist
at org.elasticsearch.ingest.PipelineExecutionService.getPipeline(PipelineExecutionService.java:193) ~[elasticsearch-5.3.1.jar:5.3.1]
at org.elasticsearch.ingest.PipelineExecutionService.access$100(PipelineExecutionService.java:41) ~[elasticsearch-5.3.1.jar:5.3.1]
at org.elasticsearch.ingest.PipelineExecutionService$2.doRun(PipelineExecutionService.java:88) [elasticsearch-5.3.1.jar:5.3.1]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:638) [elasticsearch-5.3.1.jar:5.3.1]
at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-5.3.1.jar:5.3.1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_111]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_111]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_111]

Am afraid this could kill the server,any help or suggestion how to fix this issue .
Would be really helpful.

Thanks in advance,
Raj


(Nik Everett) #2

This usually happens when you've disable ingest on a cluster to which you are sending monitoring data. Monitoring prefers that that stay on. If you set use_ingest to false on the exporting system it ought to work though.


(Raj) #3

Thank you Nik, very much for the info , it worked :slight_smile:


(system) #4

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