Track the actor that triggers the minion task #14829
Open
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.
Description
Minion task can be triggered by 3 ways as of now
To identify which actor triggered a particular task run, this PR injects the information in task configs so that it gets tracked in zk for reference.
The
triggeredBy
info is also made available onTaskDebugInfo
andSubtaskDebugInfo
.Refactor on
PinotTaskManager
There were too many derivations of schedule methods in PinotTaskManager based on what combination of tables and task types are supposed to be scheduled. This made the changes on schedule inputs hard to manage.
This PR adds a wrapper class
TaskSchedulingContext
that will be passed to only onescheduleTasks()
method to achieve all the derivations.