[
https://issues.apache.org/jira/browse/SAMZA-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740725#comment-13740725
]
Chris Riccomini commented on SAMZA-14:
--------------------------------------
logging stacktrace: Thinking more on this. Actually, rather than retry vs.
fail, I think we should continue always retrying, as we do now. The only
difference would be whether we log with ", e)" or with "e.getMessage". In
expected ("ignore the stack trace") cases, we should log with e.getMessage. In
unexpected cases, we should log your way. The reason I'm not a huge fan of
failing is that a better outcome is to just halt the job or significantly
affect the job's metrics to trigger alerts (which repeated exceptions in KCM,
KSP, and KSC would all do). This gives me a chance to debug a running process,
vs. just having logs and metrics.
> Fix misc bugs in QA jobs
> ------------------------
>
> Key: SAMZA-14
> URL: https://issues.apache.org/jira/browse/SAMZA-14
> Project: Samza
> Issue Type: Bug
> Reporter: Jay Kreps
> Assignee: Jay Kreps
> Attachments: SAMZA-14-v1.patch
>
>
> Some bugs that have already been there and some that came with the various
> package refactorings.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
