[
https://issues.apache.org/jira/browse/BEAM-6190?focusedWorklogId=175549&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-175549
]
ASF GitHub Bot logged work on BEAM-6190:
----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Dec/18 19:07
Start Date: 14/Dec/18 19:07
Worklog Time Spent: 10m
Work Description: pabloem commented on issue #7240: [BEAM-6190] Add
processing stuck message to Pantheon.
URL: https://github.com/apache/beam/pull/7240#issuecomment-447423853
I don't know what's your LDAP. Mine is pabloem@ - talk to me in hangouts?
----------------------------------------------------------------
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: 175549)
Time Spent: 1h 10m (was: 1h)
Remaining Estimate: 22h 50m (was: 23h)
> "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 10m
> Remaining Estimate: 22h 50m
>
> 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)
