-
Notifications
You must be signed in to change notification settings - Fork 136
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
Preserve component state on upgrade #2207
Conversation
🌐 Coverage report
|
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 good, be sure to revert the defaultBeatVersion
before merge.
version/version.go
Outdated
@@ -4,4 +4,4 @@ | |||
|
|||
package version | |||
|
|||
const defaultBeatVersion = "8.7.0" | |||
const defaultBeatVersion = "8.6.0" |
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.
This needs to be removed before merge 😄
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.
oooh
What does this PR do?
This PR copies run directory from stale agent to a new version of agent. Component can then pick up the state and continue where it was interrupted. This prevents creating duplicate events.
Why is it important?
Without this component loses state and can process whole file (in case of logs) again generating a lot of duplicate entries
Checklist
./changelog/fragments
using the changelog toolFixes: #2136