-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Entity Analytics] [Entity Store] Run init requests sequentially to prevent resource exists error #198268
Merged
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
tiansivive
added
release_note:skip
Skip the PR/issue when compiling release notes
v9.0.0
Theme: entity_analytics
Team:Entity Analytics
Security Entity Analytics Team
v8.16.0
backport:version
Backport to applied version labels
labels
Oct 30, 2024
Pinging @elastic/security-entity-analytics (Team:Entity Analytics) |
machadoum
approved these changes
Oct 30, 2024
Starting backport for target branches: 8.16 |
💚 Build Succeeded
Metrics [docs]Async chunks
History
|
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
tiansivive
added a commit
to tiansivive/kibana
that referenced
this pull request
Oct 31, 2024
…revent resource exists error (elastic#198268) ## Summary This PR fixes an issue where running init for both `user` and `host` entity engines in parallel would cause a race condition while enabling the risk engine, resulting in a `Resource already exists` error. --------- Co-authored-by: kibanamachine <[email protected]> (cherry picked from commit 6a50066)
tiansivive
added a commit
to tiansivive/kibana
that referenced
this pull request
Oct 31, 2024
…revent resource exists error (elastic#198268) ## Summary This PR fixes an issue where running init for both `user` and `host` entity engines in parallel would cause a race condition while enabling the risk engine, resulting in a `Resource already exists` error. --------- Co-authored-by: kibanamachine <[email protected]> (cherry picked from commit 6a50066)
tiansivive
added a commit
that referenced
this pull request
Oct 31, 2024
…y to prevent resource exists error (#198268) (#198476) # Backport This will backport the following commits from `main` to `8.x`: - [Entity Analytics] [Entity Store] Run init requests sequentially to prevent resource exists error (#198268) (6a50066) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tiago Vila Verde","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-10-30T16:03:07Z","message":"[Entity Analytics] [Entity Store] Run init requests sequentially to prevent resource exists error (#198268)\n\n## Summary\r\n\r\nThis PR fixes an issue where running init for both `user` and `host`\r\nentity engines in parallel would cause a race condition while enabling\r\nthe risk engine, resulting in a `Resource already exists` error.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"6a50066e00ae38a64c5365fd66b4dc32857ba1fc"},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[]}] BACKPORT-->
tiansivive
added a commit
that referenced
this pull request
Oct 31, 2024
…ly to prevent resource exists error (#198268) (#198477) # Backport This will backport the following commits from `main` to `8.16`: - [Entity Analytics] [Entity Store] Run init requests sequentially to prevent resource exists error (#198268) (6a50066) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tiago Vila Verde","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-10-30T16:03:07Z","message":"[Entity Analytics] [Entity Store] Run init requests sequentially to prevent resource exists error (#198268)\n\n## Summary\r\n\r\nThis PR fixes an issue where running init for both `user` and `host`\r\nentity engines in parallel would cause a race condition while enabling\r\nthe risk engine, resulting in a `Resource already exists` error.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"6a50066e00ae38a64c5365fd66b4dc32857ba1fc"},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[]}] BACKPORT-->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport:version
Backport to applied version labels
release_note:skip
Skip the PR/issue when compiling release notes
Team:Entity Analytics
Security Entity Analytics Team
Theme: entity_analytics
v8.16.0
v9.0.0
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.
Summary
This PR fixes an issue where running init for both
user
andhost
entity engines in parallel would cause a race condition while enabling the risk engine, resulting in aResource already exists
error.