[
https://issues.apache.org/jira/browse/BEAM-6190?focusedWorklogId=175127&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-175127
]
ASF GitHub Bot logged work on BEAM-6190:
----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Dec/18 01:22
Start Date: 14/Dec/18 01:22
Worklog Time Spent: 10m
Work Description: dustin12 commented on issue #7240: [BEAM-6190] Add
processing stuck message to Pantheon.
URL: https://github.com/apache/beam/pull/7240#issuecomment-447180448
@pabloem
- I have tested it on dataflow and have included a screenshot in my CL of
where this shows up along with an example pipeline. To be honest this is my
first code change at Google and I'm not really sure what information I'm free
to copy over from internal tools to external ones so I probably played it a bit
too safe. I'm guessing its fine for me to post a link to a pantheon screenshot
here? What about a link to the internal CL/Bug?
- I agree, unfortunately this seems the only channel to surface
Warnings/Errors from the Worker to the Job Logs/Pantheon main page. I have
tested to make sure that surfacing this as an error does not cause the job to
throw out the results. For example if I have a ParDo Step that takes 6 minutes
and I let the pipeline run for 19 minutes I get 3 errors reported (one for each
processElement > 5 min) and 3 items in the output collection for that step.
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 175127)
Time Spent: 1h (was: 50m)
Remaining Estimate: 23h (was: 23h 10m)
> "Processing stuck" messages should be visible on Pantheon
> ---------------------------------------------------------
>
> Key: BEAM-6190
> URL: https://issues.apache.org/jira/browse/BEAM-6190
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Affects Versions: 2.8.0
> Environment: Running on Google Cloud Dataflow
> Reporter: Dustin Rhodes
> Assignee: Dustin Rhodes
> Priority: Minor
> Fix For: Not applicable
>
> Original Estimate: 24h
> Time Spent: 1h
> Remaining Estimate: 23h
>
> When user processing results in an exception, it is clearly visible on the
> Pantheon landing page for a streaming Dataflow job. But when user processing
> becomes stuck, there is no indication, even though the worker logs it. Most
> users don't check worker logs and it is not that convenient to check for most
> users. Ideally a stuck worker would result in a visible error on the
> Pantheon landing page.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
