[
https://issues.apache.org/jira/browse/BEAM-6191?focusedWorklogId=175089&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-175089
]
ASF GitHub Bot logged work on BEAM-6191:
----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Dec/18 22:52
Start Date: 13/Dec/18 22:52
Worklog Time Spent: 10m
Work Description: foegler commented on issue #7220: [BEAM-6191] Remove
redundant error logging for Dataflow exception handling
URL: https://github.com/apache/beam/pull/7220#issuecomment-447150375
Sorry! What's the notification mechanism used here so I know to watch for
it?
Does that OOM message actually come through? Don't think I've ever seen it,
but it'd sure be handy!
LGTM
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 175089)
Time Spent: 40m (was: 0.5h)
> Redundant error messages for failures in Dataflow runner
> --------------------------------------------------------
>
> Key: BEAM-6191
> URL: https://issues.apache.org/jira/browse/BEAM-6191
> Project: Beam
> Issue Type: New Feature
> Components: runner-dataflow
> Reporter: Scott Wegner
> Assignee: Scott Wegner
> Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The Dataflow runner harness has redundant error logging from a couple
> different components, which creates log spam and confusion when failures do
> occur. We should dedupe redundant logs.
> From a typical user-code exception, we see at least 3 error logs from the
> worker:
> http://screen/QZxsJOVnvt6
> "Aborting operations"
> "Uncaught exception occurred during work unit execution. This will be
> retried."
> "Failure processing work item"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
