You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Dustin Rhodes (JIRA)" <ji...@apache.org> on 2019/01/29 23:05:00 UTC

[jira] [Closed] (BEAM-6190) "Processing stuck" messages should be visible on Pantheon

     [ https://issues.apache.org/jira/browse/BEAM-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dustin Rhodes closed BEAM-6190.
-------------------------------

Verified it is now reported in prod.

> "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 40m
>  Remaining Estimate: 22h 20m
>
> 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)