-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
track progress from within segment processor framework #9457
track progress from within segment processor framework #9457
Conversation
e.g. for those progress status from SegmentProcessorFramework:
|
dba00aa
to
4143030
Compare
} catch (Exception e) { | ||
_eventObserver.notifyTaskError(pinotTaskConfig, e); | ||
_minionMetrics.addMeteredTableValue(taskType, MinionMeter.NUMBER_TASKS_FAILED, 1L); | ||
LOGGER.error("Caught exception while executing task: {}", _taskConfig.getId(), e); | ||
return new TaskResult(TaskResult.Status.FAILED, e.toString()); | ||
return new TaskResult(TaskResult.Status.FAILED, StringUtil.getStackTraceAsString(e)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
e.toString() like e.getMessage() just returns the error msg (basically the first line of the stack trace).
4143030
to
1474e92
Compare
and keep full exception stack trace instead of the top line in task info field
1474e92
to
d28ab78
Compare
pinot-core/src/main/java/org/apache/pinot/core/segment/processing/mapper/SegmentMapper.java
Outdated
Show resolved
Hide resolved
0bd1905
to
178eaa2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* track progress from within segment processor framework and keep full exception stack trace instead of the top line in task info field * cr
Follow up on #9449 to get finer grained progress status from SegmentProcessorFramework as well, as that's usually the step takes most of task time, breaking it down to map/reduce/generation steps for now.