-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
LogStash::Pipeline when collecting metrics in the pipeline global metric populates the different metrics #7724
Comments
@jakelandis since we had a few recent changes in the metrics subsystem, can I ask you to take a look at this? |
@jsvd - Taking a look. |
I could not reproduce locally, and the failures appear intermittent on our build systems. It seem like when it does error, the error stems from the first test run. I will add retry logic to these tests. For example:
BAD
ANOTHER BAD:
|
looking at the line where the error happens, pipeline_spec.rb:805, the failure comes from the |
@jsvd - Thanks! I missed that. Explains why the tests still intermittently fail even with the retry. |
I am reopening - this re-pop'ed in 6.0 build. Was the fix backported in 6 ? |
@colinsurprenant - It looks like it a25d329 was missed for 6.0 and 6.x I will see if Jarvis can merge #7728 to 6.0 and 6.x EDIT: Nope ... will manually backpatch. |
@colinsurprenant - I was wrong it is in 6.0/6.x. It appears this change was in before the 6.0 feature freeze, so there was no need to backport. The fix was just adding more retries, so it was not much of an actual fix. |
suggestions? ignore? more retries? |
This is still happening occasionally even with the Java Pipeline, preceded by error indicading that workers failed to initialize:
|
Examples:
https://travis-ci.org/elastic/logstash/jobs/254799125#L7518-L7544
https://logstash-ci.elastic.co/job/elastic+logstash+master+multijob-unix-compatibility/os=fedora/26/console
The text was updated successfully, but these errors were encountered: