On a first look things looked normal since you weren't supplying anything on stdin so Logstash would naturally wait for input, but a) unless this has changed in Logstash 5 it'll log something to stdout to indicate that it's alive and b) 13 seconds of CPU time just for starting up sounds excessive.
It turned out that if I had waited just a little longer, after about 5 minutes logstash does start and work as expected.
Not quite sure what the 5 minute mark was about, some kind of timeout perhaps, but what it's waiting for was unclear to me.
In either case I moved on with the setup, and got logstash working, so while the time it took for logstash to start in my example was annoying, ultimately it turned out to be a red herring. It does not take 5 min for logstash to start up when the full setup is inplace, as opposed to the the inline config sample above.
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.