As it says, that is a bug. Does logstash log a stack trace? If so, please post it. If not, someone will have to run it in a debugger, reproduce the problem and set a breakpoint on the init of a RuntimeException and get the stack trace that way. If you have the skill set to do so, please post the stack trace. If not, I would suggest downgrading to 6.0.5.
Its happening due to the following issue - https://github.com/jruby/jruby/issues/6038
Fixed in logstash 7.10+ so anyone facing this issue has option to either upgrade the logstash version or revert back to original version of beats 6.0.5(recommended)
Ps - I've noticed that Logstash7.5 works fine with 6.0.11 version of beats. We are testing this but its too early to say that it works completely with any issues. I'll update this thread in couple of days with my findings with the revised beats plugin
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.