[ML] Move datafeed stats action off of master node #82271
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
Previously the get datafeed stats action was handled on the master node. This dated back to the time when datafeed configs were stored in the cluster state. Now that the action consists of running a series of searches it can be a handled transport action.
|
Jenkins run elasticsearch-ci/bwc |
2 similar comments
|
Jenkins run elasticsearch-ci/bwc |
|
Jenkins run elasticsearch-ci/bwc |
|
Pinging @elastic/ml-core (Team:ML) |
benwtrent
approved these changes
Jan 5, 2022
droberts195
added
the
auto-backport-and-merge
💔 Backport failed
You can use sqren/backport to manually backport by running |
droberts195
added a commit
to droberts195/elasticsearch
that referenced
this pull request
Jan 6, 2022
Previously the get datafeed stats action was handled on the master node. This dated back to the time when datafeed configs were stored in the cluster state. Now that the action consists of running a series of searches it can be a handled transport action. Backport of elastic#82271
This was referenced Jan 6, 2022
droberts195
added a commit
that referenced
this pull request
Jan 6, 2022
Previously the get datafeed stats action was handled on the master node. This dated back to the time when datafeed configs were stored in the cluster state. Now that the action consists of running a series of searches it can be a handled transport action. Backport of #82271
droberts195
added a commit
that referenced
this pull request
Jan 6, 2022
Previously the get datafeed stats action was handled on the master node. This dated back to the time when datafeed configs were stored in the cluster state. Now that the action consists of running a series of searches it can be a handled transport action. Backport of #82271
astefan
pushed a commit
to astefan/elasticsearch
that referenced
this pull request
Jan 7, 2022
Previously the get datafeed stats action was handled on the master node. This dated back to the time when datafeed configs were stored in the cluster state. Now that the action consists of running a series of searches it can be a handled transport action.
astefan
pushed a commit
to astefan/elasticsearch
that referenced
this pull request
Jan 7, 2022
Previously the get datafeed stats action was handled on the master node. This dated back to the time when datafeed configs were stored in the cluster state. Now that the action consists of running a series of searches it can be a handled transport action.
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.
Previously the get datafeed stats action was handled on the
master node. This dated back to the time when datafeed configs
were stored in the cluster state. Now that the action consists
of running a series of searches it can be a handled transport
action.