Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

securityonion-elastic: enable Java Execution Engine in Logstash #1436

Closed
dougburks opened this issue Feb 2, 2019 · 5 comments

Comments

Projects
2 participants
@dougburks
Copy link
Contributor

commented Feb 2, 2019

Add the following to logstash.yml:

# Java Execution Engine provides much better performance
pipeline.java_execution: true

Add the following to jvm.options:

# Avoid StackOverflowError when enabling Java Execution Engine
# https://github.com/elastic/logstash/issues/10131
-Xss16M

@dougburks dougburks added this to To do in 16.04.6.1 via automation Feb 2, 2019

@dougburks dougburks moved this from To do to In progress in 16.04.6.1 Feb 2, 2019

dougburks added a commit to Security-Onion-Solutions/securityonion-elastic that referenced this issue Feb 2, 2019

@mattkaar

This comment has been minimized.

Copy link

commented Feb 12, 2019

Just wanted to say thanks for this fix! I was troubleshooting slow Logstash startup (~10m) on a fresh 16.04.5.6 install, and this brought it down to <2m.

@dougburks

This comment has been minimized.

Copy link
Contributor Author

commented Feb 12, 2019

Hi @mattkaar ,

Thanks, we're excited about the improved Logstash startup as well!

Please note that if you're on 16.04.5.6, then you're running Logstash 6.5 and Java Execution Engine is considered Beta. It's been promoted to GA in Logstash 6.6 and so we are rolling this out to all users along with our 6.6 Docker images.

@mattkaar

This comment has been minimized.

Copy link

commented Feb 12, 2019

@dougburks Good to know! This is for a training environment, so I'll take the improved startup time over the risks of the beta. Looking forward to the same with Logstash 6.6.

@dougburks dougburks self-assigned this Feb 13, 2019

@dougburks dougburks removed this from In progress in 16.04.6.1 Mar 22, 2019

@dougburks dougburks added this to To do in 16.04.6.2 Mar 22, 2019

@dougburks dougburks removed this from To do in 16.04.6.2 Mar 29, 2019

@dougburks dougburks added this to To do in 16.04.6.1 via automation Mar 29, 2019

@dougburks dougburks moved this from To do to In progress in 16.04.6.1 Apr 2, 2019

dougburks added a commit to Security-Onion-Solutions/securityonion-elastic that referenced this issue Apr 2, 2019

@dougburks

This comment has been minimized.

Copy link
Contributor Author

commented May 3, 2019

@dougburks dougburks moved this from In progress to In Testing in 16.04.6.1 May 3, 2019

@dougburks

This comment has been minimized.

@dougburks dougburks closed this May 13, 2019

16.04.6.1 automation moved this from In Testing to Done May 13, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.