-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Fix panic when MaxRetryInterval is specified, but RetryInterval is not #35820
Conversation
💚 CLA has been signed |
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
Pinging @elastic/elastic-agent (Team:Elastic-Agent) |
/test |
Is there any chance that this fix be backported to 7.x? |
Let's wait for @faec's review here but no blocking point to have it backported in 7.17 on my side. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks for finding this!
Looks good, I will start the backports, I think we're on track to make the impending release cuts for 7.x and 8.9 |
Backports merged! I will follow up soon with a unit test but this fix should appear in the releases later this month |
What does this PR do?
In disk queue configuration, it seems like the
MaxRetryInterval
is read from the wrong field, which leads to a panic whenRetryInterval
is not provided.Also,
MaxRetryInterval
doesn't seem configurable at all as it is.Why is it important?
So
MaxRetryInterval
can be configuredChecklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Logs