[Auditbeat] System module: Fix and unify bucket closing logic #10897
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cwurm
added
bug
review
needs_backport
|
Pinging @elastic/secops |
andrewkroh
approved these changes
Feb 28, 2019
added 2 commits
March 1, 2019 15:13
cwurm
pushed a commit
to cwurm/beats
that referenced
this pull request
Mar 1, 2019
…c#10897) The `host` dataset is erroneously trying to save state in its `Close()` method. It should have saved the state earlier - usually at the end of `Fetch()` - and then should only close the bucket (something it is not doing at all). At the same time, it is not saving state in its `reportState()` method. Combined, this can lead to an error when the dataset is terminated before the first regular `reportChanges()` is run. This fixes both issues and furthermore unifies the bucket closing logic across all six datasets of the System module. (cherry picked from commit e007c9c)
cwurm
added
v7.2.0
and removed
needs_backport
cwurm
pushed a commit
to cwurm/beats
that referenced
this pull request
Mar 1, 2019
…c#10897) The `host` dataset is erroneously trying to save state in its `Close()` method. It should have saved the state earlier - usually at the end of `Fetch()` - and then should only close the bucket (something it is not doing at all). At the same time, it is not saving state in its `reportState()` method. Combined, this can lead to an error when the dataset is terminated before the first regular `reportChanges()` is run. This fixes both issues and furthermore unifies the bucket closing logic across all six datasets of the System module. (cherry picked from commit e007c9c)
cwurm
pushed a commit
to cwurm/beats
that referenced
this pull request
Mar 1, 2019
…c#10897) The `host` dataset is erroneously trying to save state in its `Close()` method. It should have saved the state earlier - usually at the end of `Fetch()` - and then should only close the bucket (something it is not doing at all). At the same time, it is not saving state in its `reportState()` method. Combined, this can lead to an error when the dataset is terminated before the first regular `reportChanges()` is run. This fixes both issues and furthermore unifies the bucket closing logic across all six datasets of the System module. (cherry picked from commit e007c9c)
cwurm
pushed a commit
to cwurm/beats
that referenced
this pull request
Mar 5, 2019
…c#10897) The `host` dataset is erroneously trying to save state in its `Close()` method. It should have saved the state earlier - usually at the end of `Fetch()` - and then should only close the bucket (something it is not doing at all). At the same time, it is not saving state in its `reportState()` method. Combined, this can lead to an error when the dataset is terminated before the first regular `reportChanges()` is run. This fixes both issues and furthermore unifies the bucket closing logic across all six datasets of the System module. (cherry picked from commit e007c9c)
cwurm
pushed a commit
that referenced
this pull request
Mar 5, 2019
…ucket closing logic (#11026) Cherry-pick of PR #10897 to 7.x branch. Original message: The `host` dataset is erroneously trying to save state in its `Close()` method. It should have saved the state earlier - usually at the end of `Fetch()` - and then should only close the bucket (something it is not doing at all). At the same time, it is not saving state in its `reportState()` method. Combined, this can lead to an error when the dataset is terminated before the first regular `reportChanges()` is run. This fixes both issues and furthermore unifies the bucket closing logic across all six datasets of the System module.
cwurm
pushed a commit
that referenced
this pull request
Mar 5, 2019
#11027) The `host` dataset is erroneously trying to save state in its `Close()` method. It should have saved the state earlier - usually at the end of `Fetch()` - and then should only close the bucket (something it is not doing at all). At the same time, it is not saving state in its `reportState()` method. Combined, this can lead to an error when the dataset is terminated before the first regular `reportChanges()` is run. This fixes both issues and furthermore unifies the bucket closing logic across all six datasets of the System module. (cherry picked from commit e007c9c)
cwurm
pushed a commit
that referenced
this pull request
Mar 5, 2019
…ucket closing logic (#11029) Cherry-pick of PR #10897 to 6.6 branch. Original message: The `host` dataset is erroneously trying to save state in its `Close()` method. It should have saved the state earlier - usually at the end of `Fetch()` - and then should only close the bucket (something it is not doing at all). At the same time, it is not saving state in its `reportState()` method. Combined, this can lead to an error when the dataset is terminated before the first regular `reportChanges()` is run. This fixes both issues and furthermore unifies the bucket closing logic across all six datasets of the System module.
cwurm
pushed a commit
that referenced
this pull request
Mar 6, 2019
…ucket closing logic (#11028) Cherry-pick of PR #10897 to 6.7 branch. Original message: The `host` dataset is erroneously trying to save state in its `Close()` method. It should have saved the state earlier - usually at the end of `Fetch()` - and then should only close the bucket (something it is not doing at all). At the same time, it is not saving state in its `reportState()` method. Combined, this can lead to an error when the dataset is terminated before the first regular `reportChanges()` is run. This fixes both issues and furthermore unifies the bucket closing logic across all six datasets of the System module.
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…unify bucket closing logic (elastic#11029) Cherry-pick of PR elastic#10897 to 6.6 branch. Original message: The `host` dataset is erroneously trying to save state in its `Close()` method. It should have saved the state earlier - usually at the end of `Fetch()` - and then should only close the bucket (something it is not doing at all). At the same time, it is not saving state in its `reportState()` method. Combined, this can lead to an error when the dataset is terminated before the first regular `reportChanges()` is run. This fixes both issues and furthermore unifies the bucket closing logic across all six datasets of the System module.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
hostdataset is erroneously trying to save state in itsClose()method. It should have saved the state earlier - usually at the end ofFetch()- and then should only close the bucket (something it is not doing at all). At the same time, it is not saving state in itsreportState()method. Combined, this can lead to an error when the dataset is terminated before the first regularreportChanges()is run.This fixes both issues and furthermore unifies the bucket closing logic across all six datasets of the System module.