Fork TransportRollupCapsAction to MANAGEMENT POOL#89803
Merged
original-brownbear merged 2 commits intoelastic:mainfrom Sep 6, 2022
original-brownbear:fork-rollup-caps
Merged
Fork TransportRollupCapsAction to MANAGEMENT POOL#89803original-brownbear merged 2 commits intoelastic:mainfrom original-brownbear:fork-rollup-caps
original-brownbear merged 2 commits intoelastic:mainfrom
original-brownbear:fork-rollup-caps
Conversation
We can't run these actions on the transport threads in their current form. The fully deserialize the mapping for each index they inspect which will take a massive amount of time if either a large number of indices or a large number of fields (indices * fields_per_index) overall are inspected.
Collaborator
|
Pinging @elastic/es-analytics-geo (Team:Analytics) |
Collaborator
|
Hi @original-brownbear, I've created a changelog YAML for you. |
pxsalehi
reviewed
Sep 5, 2022
| @@ -0,0 +1,5 @@ | |||
| pr: 89803 | |||
| summary: Fork `TransportRollupCapsAction` to MANAGEMENT POOL | |||
Member
There was a problem hiding this comment.
Is it important to mention the exact names of the two affected Transport Actions here?
Contributor
Author
There was a problem hiding this comment.
This was just generated from the PR description and there I think it's nice for people searching for similar issues to have the exact name.
idegtiarenko
approved these changes
Sep 5, 2022
Contributor
Author
|
Thanks you two! |
This was referenced Sep 6, 2022
Collaborator
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 6, 2022
We can't run these actions on the transport threads in their current form. The fully deserialize the mapping for each index they inspect which will take a massive amount of time if either a large number of indices or a large number of fields (indices * fields_per_index) overall are inspected.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Sep 6, 2022
We can't run these actions on the transport threads in their current form. The fully deserialize the mapping for each index they inspect which will take a massive amount of time if either a large number of indices or a large number of fields (indices * fields_per_index) overall are inspected.
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
4 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.
We can't run these actions on the transport threads in their current form.
The fully deserialize the mapping for each index they inspect which will
take a massive amount of time if either a large number of indices or a large
number of fields (indices * fields_per_index) overall are inspected.