[ML] Fix serialization of datafeed running state for relocated datafeed #75929
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
The datafeed running state was set to null for a datafeed that had recently moved to a different node. This resulted in an exception while serializing between nodes (but would also cause incomplete information in the datafeed stats response). This change makes the datafeed running state return the best information available in this case: - real_time_configured will return the correct value - real_time_running will return false, which is reasonable since the datafeed has yet got started on the new node Backport of elastic#75923
droberts195
added
backport
auto-merge-without-approval
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.
The datafeed running state was set to null for a datafeed that
had recently moved to a different node. This resulted in an
exception while serializing between nodes (but would also
cause incomplete information in the datafeed stats response).
This change makes the datafeed running state return the best
information available in this case:
since the datafeed has yet got started on the new node
Backport of #75923