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 2022/01/12 18:28:01 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=17474827#comment-17474827 ] 

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

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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
>            Priority: P2
>              Labels: portability-flink, portability-spark, stale-P2
>
> 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.20.1#820001)