Open samary opened 4 years ago
Same issue since upgrade to 7.6.2. No problem with 7.5.2...
Bug not related to Elasticsearch. I have also an error with filter/mutate for example.
Any update on this ticket? Is it resolved or still happening? I have the same problem.
I don't have any proper solution. I worked around this issue by developping in multiple files and combine them on deployment. I will test the version 7.7 with the pipeline ordering mechanism. I hope it will solve my issue.
Looks like issue is resolved with "java_execution" in 7.7.0. No need to enable the flag in this version as it is expected to work with java. I will post my results soon.
Same problem with 7.7.1 when I set pipeline.java_execution to false
I tested 7.7.0 with --pipeline.workers 1 --pipeline.ordered true
and keeping java_execution enabled and it works without any error now.
I'm closing this issue.
The initial problem is "Disable the java_execution and split pipeline configuration in multiple files", I don't understand why the ticket is closed and the java_execution enabled option.
Agree with @duylong if Logstash not starting with "java_execution: false", ticket should be still open.
@duylong what are you trying achieve by disabling java execution? For me event ordering is the problem and hoping that is resolved in 7.7.0 with java execution enabled (default setting). Testing that fix right now.
I have a complex configuration in several files, java execution enabled does not work for me, the loading is long and endless. Everything worked fine since version 7.5.2, now I have this error and I can no longer upgrade.
@duylong : Indeed, the root cause is not solved. But for my use case, the only requirement I had was to ensure the event ordering (worked around by disabling the java_execution), but since it is now working with it enabled, this is fine by me.
I don't really get why you need to disable the java_execution and I think you will need to find a way to get your config working with it since I think the ruby worker will be decommissionned in 8.0 if I remember well.
I'm reopening it then since this is not really solved for your use case.
Hi,
I'm facing the following error when I disable the java_execution and split my configuration into multiple files :
Failed to execute action {:action=>LogStash::PipelineAction::Create/pipeline_id:main, :exception=>"LogStash::ConfigurationError", :message=>"Could not determine ID for output/elasticsearch, source don't matched: [file]/etc/logstash/conf.d/tests/002_output.conf
It works fine when I enable the java_execution (see output below) but I need to disable it since I need to receive events in the correct order use the aggregate plugin. It also worked in previous versions (7.5.2 and 7.4.1).
My different tests show the problem it is not related to the content of the config itself (I also tested different outputs like stdout and reordering the files) but rather in the configuration loading mechanism itself: it always fails on the second file.
Thanks for your help.
Kind regards,
Samir
General information.
001_input.conf
002_output.conf
Here are the debug outputs of the 2 differents command (without and with java_execution) :