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

Auto Reload considered dangerous? #41

Closed
kenwdelong opened this Issue May 3, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@kenwdelong
Contributor

kenwdelong commented May 3, 2016

I just wanted to make you aware of another issue that I had with the 2.3.x series. There might be a resource leak in logstash. The issue is tracking here: elastic/logstash#5235.

Once I removed auto-reload from my logstash config, my instance is fine. It's still running with load average 0.1 after 2 days.

@spujadas

This comment has been minimized.

Show comment
Hide comment
@spujadas

spujadas May 3, 2016

Owner

Ouch! Thanks for the heads up, will most certainly consider removing it as a default option (users can always enable it voluntarily using the env vars) and/or flagging it in the documentation.

Owner

spujadas commented May 3, 2016

Ouch! Thanks for the heads up, will most certainly consider removing it as a default option (users can always enable it voluntarily using the env vars) and/or flagging it in the documentation.

spujadas added a commit that referenced this issue May 3, 2016

@spujadas

This comment has been minimized.

Show comment
Hide comment
@spujadas

spujadas May 3, 2016

Owner

Thanks again – will keep track of the Elasticsearch issue.

Owner

spujadas commented May 3, 2016

Thanks again – will keep track of the Elasticsearch issue.

@spujadas spujadas closed this May 3, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment