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

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/06/04 04:02:00 UTC

[jira] [Commented] (BEAM-7796) Improve health signal for StreamingDataflowWorker

    [ https://issues.apache.org/jira/browse/BEAM-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17547870#comment-17547870 ] 

Kenneth Knowles commented on BEAM-7796:
---------------------------------------

This issue has been migrated to https://github.com/apache/beam/issues/19581

> Improve health signal for StreamingDataflowWorker
> -------------------------------------------------
>
>                 Key: BEAM-7796
>                 URL: https://issues.apache.org/jira/browse/BEAM-7796
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-dataflow
>            Reporter: Sam Whittle
>            Priority: P3
>
> The StreamingDataflowWorker currently just uses the health of the FnAPI server for its own health monitoring.  It should also take into account persistent failures to process work items successfully which may be due to a bad worker.  For example, a recent Snappy initialization error was due to /tmp becoming full.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)