Bugfix: Validate minionInstanceTag during task-generation #13092
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.
label:
bugfix
minion
This patch validates whether the configured minionInstanceTag actually exists in the list of instance-tags or not. Before this, if a wrong instanceTag was configured for a task, Pinot scheduled those tasks and they got stuck in
IN_PROGRESS
state. Until the task is timed out, no another task scheduling for that table and task type was possible. Or you need to update some minion instance with the specified instanceTag. Ideally, we should error out by throwing an exception for instanceTag not found which this patch achieves.There is a more proactive way of doing this at table-config updation itself. We will try to achieve that when we introduce
minionTenant
config itself.