You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/10/16 17:25:00 UTC

[jira] [Commented] (BEAM-12902) Better error messages for misconfigured Beam worker

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

Beam JIRA Bot commented on BEAM-12902:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> Better error messages for misconfigured Beam worker
> ---------------------------------------------------
>
>                 Key: BEAM-12902
>                 URL: https://issues.apache.org/jira/browse/BEAM-12902
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-flink, runner-spark
>            Reporter: Kyle Weaver
>            Assignee: Kyle Weaver
>            Priority: P2
>              Labels: portability-flink, portability-spark, stale-assigned
>
> If the Beam portable worker is misconfigured, error messages are usually just generic "Connection refused"-type messages that aren't actionable unless the user knows about Beam internals (which they shouldn't have to).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)