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
Issue #1590 Multiline filter and additional worker threads do not work together. #1591
Conversation
Can one of the admins verify this patch? |
Thanks. LGTM. |
To be honest, I'd rather just fix the multiline filter to be threadsafe, but we'll go with this patch for now. |
Issue #1590 Multiline filter and additional worker threads do not work together.
Hi @jordansissel, Is there any estimated time for the fix of multiline filter to be threadsafe? I asked already an alternative solution here: #1754 (comment) Thanks in advance, |
@varh1i When we had this issue in our prod environment and was struggling with performance, we came up with the below solution. Logstash receiver -> Redis -> Logstash indexers (3 instances per 4 core) -> Elasticsearch on the same box. Not ideal but worked for our performance needs. Logstash indexers consume 1 core for the worker and then shared the remaining core for input / outputs. cheers, |
Thank you @lmorfitt for the suggestion, I got a similar response from SO too, will give it a try :) |
Hi There, We have a new ELK environment which we love, the only thing making it lame at the moment is the multiline filter not being threadsafe - we have a big setup. Any chance this can happen? :) |
Please fix this bug, we are using Kafka+Logstash, in order to leverage the partition capability, we may enable the logstash multiple worker threads functions. At least, ES should provide a work around. Thanks! |
Simple documentation update to show this is a limitation with the filter.
#1590