sajjad-moradi commented on code in PR #9058:
URL: https://github.com/apache/pinot/pull/9058#discussion_r922894155
##########
pinot-controller/src/main/java/org/apache/pinot/controller/api/resources/PinotTaskRestletResource.java:
##########
@@ -231,6 +236,23 @@ public Map<String,
PinotHelixTaskResourceManager.TaskDebugInfo> getTasksDebugInf
return _pinotHelixTaskResourceManager.getTasksDebugInfoByTable(taskType,
tableNameWithType, verbosity);
}
+ @GET
+ @Path("/tasks/generator/{tableNameWithType}/{taskType}/debug")
+ @ApiOperation("Fetch task generation information for the recent runs of the
given task for the given table")
+ public BaseTaskGeneratorInfo getTaskGenerationDebugInto(
+ @ApiParam(value = "Task type", required = true) @PathParam("taskType")
String taskType,
+ @ApiParam(value = "Table name with type", required = true)
@PathParam("tableNameWithType")
+ String tableNameWithType) {
+ BaseTaskGeneratorInfo
+ taskGeneratorMostRecentRunInfo =
_taskManagerStatusCache.fetchTaskGeneratorInfo(tableNameWithType, taskType);
Review Comment:
There are two parts:
- generating task configurations which happens in pinot code
- submitting the task via TaskDriver which is in Helix code
Subbu has a valid point that helix should provide some info on failure on
the 2nd part - task submission. The first part though is before reaching helix
and it's good if we have an API to capture issues in task generation in pinot
code.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org
