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.

Sign up for GitHub

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

Jump to bottom

Java execution may start inputs before compilation of filters and outputs has completed. #11170

Closed
robbavey opened this issue Sep 27, 2019 · 2 comments · Fixed by #11492
Closed

Java execution may start inputs before compilation of filters and outputs has completed. #11170

robbavey opened this issue Sep 27, 2019 · 2 comments · Fixed by #11492
Labels
Java Execution

Comments

@robbavey
Copy link
Member

When processing large and complex pipelines, there may be a significant delay between the inputs starting and the compilation of the filters and outputs, which does not happen with the ruby execution.

The issue is that the compilation is done in separate threads in the constructor of the WorkerLoop, but the main thread does not wait for this to be completed before starting the inputs
@colinsurprenant colinsurprenant mentioned this issue Sep 30, 2019
Closed
8 tasks
@colinsurprenant colinsurprenant mentioned this issue Jan 13, 2020
Merged
@colinsurprenant
Copy link
Contributor

PR in #11492

@colinsurprenant colinsurprenant mentioned this issue Jan 13, 2020
Open
@colinsurprenant
Copy link
Contributor

Fix merged, will make it for 7.5.2 and 7.6.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Java Execution
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

start inputs only when all WorkerLoop are fully initialized colinsurprenant/logstash
2 participants
@colinsurprenant @robbavey