fix: Query Recommendations - Use Scheduled Retry + Use ingester_service::ingest #8920
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.
PR Type
Fix
Description
Query recommendations were adjusted to be based on triggers with retries upon failure. Instead of relying on retry, we are simply skipping this run for the next generation of query_recommendations.
Triggers and retries were used in hopes that the non-ingester node will eventually give up and an ingester node may pick up this trigger. This was a bad idea from the get go. We use ingester_service::ingest now which finds the ingester node to upload to it regardless of where the ingestions request comes from.