Skip to content
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

Cherry-pick #8240 to 6.4: Clone any cached data from docker and k8s #8246

Merged
merged 1 commit into from
Sep 6, 2018

Conversation

ph
Copy link
Contributor

@ph ph commented Sep 5, 2018

Cherry-pick of PR #8240 to 6.4 branch. Original message:

Using cached data can lead to race condition if we have some reference
in place, this commit force a clone on the retrieved data so each event
has his own copy.

Using cached data can lead to race condition if we have some reference
in place, this commit force a clone on the retrieved data so each event
has his own copy.

(cherry picked from commit 65e2e5e)
@ph ph merged commit 05437d3 into elastic:6.4 Sep 6, 2018
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
Using cached data can lead to race condition if we have some reference
in place, this commit force a clone on the retrieved data so each event
has his own copy.

(cherry picked from commit b4a69c1)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants