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

Issue #1590 Multiline filter and additional worker threads do not work together. #1591

Merged
merged 1 commit into from Aug 22, 2014

Conversation

lmorfitt
Copy link

@lmorfitt lmorfitt commented Aug 1, 2014

Simple documentation update to show this is a limitation with the filter.

#1590

@elasticsearch-release
Copy link

Can one of the admins verify this patch?

@colinsurprenant
Copy link
Contributor

Thanks. LGTM.

@colinsurprenant colinsurprenant added this to the 1.4.3 milestone Aug 6, 2014
@jordansissel jordansissel modified the milestones: 1.4.3, v1.5.0 Aug 22, 2014
@jordansissel
Copy link
Contributor

To be honest, I'd rather just fix the multiline filter to be threadsafe, but we'll go with this patch for now.

jordansissel added a commit that referenced this pull request Aug 22, 2014
Issue #1590 Multiline filter and additional worker threads do not work together.
@jordansissel jordansissel merged commit ab60853 into elastic:master Aug 22, 2014
@varh1i
Copy link

varh1i commented Mar 16, 2015

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)
but didn't get any response so added a SO question too: http://stackoverflow.com/questions/29072517/how-to-process-multilines-in-logstash-with-multiple-worker-threads

Thanks in advance,
Balazs

@lmorfitt
Copy link
Author

@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,
Luke

@varh1i
Copy link

varh1i commented Mar 17, 2015

Thank you @lmorfitt for the suggestion, I got a similar response from SO too, will give it a try :)

@synaq
Copy link

synaq commented May 23, 2015

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? :)

@davidturing
Copy link

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!
David

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants