It means that logstash is still draining events that won't necessarily be persistent should you initiate another SIGTERM against the logstash instance... from what I gather it's telling you to "wait" for it to finish draining out it's buffer.
Personally my instance has been doing this for a good long while so I'm not sure when I'm supposed to assume it's done or if it's buffer is just ginormous.
We see this periodically when the buffer empties. If your batch_size is set to an exceptionally high number, if you don't have enough worker processes assigned to the output, if you are groking the heck out of the data and haven't assigned enough grok workers... There are lots of reasons why this might take a while.
However, it should stop within due time. The other option is to hit ^C again or kill the running process.
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.