These errors could mean there is back-pressure coming from one of your outputs in Logstash. Have you checked the logs for Logstash? Do you have any monitoring in place for Logstash or the destination service to see what kind of throughput you are getting and whether things are operating normally.
Thank you so much Andrew..
I have fixed the issue..Now I am not getting any error..
But the filebeat is getting stopped after 5 minutes without any error.
Once I restart the file beat..it's shipping logs for 5 min's and then it got stopped..
So by upgrading the input plugin you fixed the keep-alive issue that causes the connection between beats and Logstash to be closed. But you still need to address the underlying issue in Logstash which is most likely some form of back-pressure (either a blocked/slow output, a poor performing logstash filter).
If you haven't checked the Logstash logs do that first.
Then take a look at the node stats for the instance. Perhaps you will spot a section in the pipeline that's taking lot's of time or has errors.
Another tool is the pipeline viewier which gives you a visualization of the pipeline with metrics about each stage.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.