Hi,
As described in title, my filebeat instance running with --once does not exit with SIGTERM. it does exit if without --once.
Here is my simple yml:
filebeat.prospectors:
- input_type: log
paths:
- /xxx
close_eof: true
output.logstash:
hosts: ["xxx:xxx"]
max_retries : -1
filebeat.shutdown_timeout: 5s
Here is the logging after sending SIGTERM:
2017-12-11T11:12:55+08:00 INFO Stopping filebeat
2017-12-11T11:12:55+08:00 INFO Prospector outlet closed
2017-12-11T11:12:55+08:00 INFO Prospector outlet closed
2017-12-11T11:12:55+08:00 INFO Prospector outlet closed
2017-12-11T11:12:55+08:00 INFO Prospector channel stopped
2017-12-11T11:12:55+08:00 WARN send event
2017-12-11T11:12:55+08:00 WARN send event
2017-12-11T11:13:00+08:00 WARN send event
2017-12-11T11:13:09+08:00 INFO Non-zero metrics in the last 30s: beat.memstats.gc_next=-2263856 beat.memstats.memory_alloc=14549368 beat.memstats.memory_total=684261736 filebeat.harvester.closed=6 filebeat.harvester.open_files=-6 filebeat.harvester.running=-6 output.events.acked=71689 output.logstash.events.acked=71689 output.logstash.publishEvents.call.count=35 output.logstash.read.bytes=396 output.logstash.write.bytes=9615104 output.write.bytes=9615104 publish.events=71696 publisher.events.count=69641 registrar.states.update=71696 registrar.writes=36
2017-12-11T11:13:39+08:00 INFO Non-zero metrics in the last 30s: beat.memstats.memory_alloc=7184 beat.memstats.memory_total=7184
is this expected behavior?