Closed tibrewalpratik17 closed 1 week ago
Attention: Patch coverage is 0%
with 4 lines
in your changes are missing coverage. Please review.
Project coverage is 62.20%. Comparing base (
59551e4
) to head (a0047f1
). Report is 419 commits behind head on master.
Files | Patch % | Lines |
---|---|---|
...controller/helix/core/minion/PinotTaskManager.java | 0.00% | 4 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@tibrewalpratik17 : let's also emit numErrorTasksScheduled
metric in a follow-up PR so we can setup alerting/monitoring
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.