Fix slow assertion running in production in RoutingNodes#88951
Merged
original-brownbear merged 1 commit intoelastic:mainfrom Jul 29, 2022
original-brownbear:fix-accidental-assert-hot-path
Merged
Fix slow assertion running in production in RoutingNodes#88951original-brownbear merged 1 commit intoelastic:mainfrom original-brownbear:fix-accidental-assert-hot-path
original-brownbear merged 1 commit intoelastic:mainfrom
original-brownbear:fix-accidental-assert-hot-path
Conversation
This needs to be in a separate method, it's currently running in production and uses significant CPU time. Broken in #88794
Collaborator
|
Pinging @elastic/es-distributed (Team:Distributed) |
Contributor
Author
|
Thanks David! Merging despite the failures since those are obvious Jenkins issue unrelated to the changes here. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This needs to be in a separate method, it's currently running in production
and uses significant CPU time.
Broken in #88794