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 2019/11/02 20:26:00 UTC
[jira] [Commented] (BEAM-8506) Failing Dataflow job should
explicitly state reason to be missing container.
[ https://issues.apache.org/jira/browse/BEAM-8506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16965491#comment-16965491 ]
Kenneth Knowles commented on BEAM-8506:
---------------------------------------
Incorrect or non-actionable messages are bugs
> Failing Dataflow job should explicitly state reason to be missing container.
> ----------------------------------------------------------------------------
>
> Key: BEAM-8506
> URL: https://issues.apache.org/jira/browse/BEAM-8506
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Reporter: Mikhail Gryzykhin
> Priority: Major
>
> [https://builds.apache.org/job/beam_PreCommit_Python_Phrase/903/]
>
> Currenlty job timeouts or states that no values were returned. Job should fail with explicit reason of "container missing".
>
> Current relevant log is description of job containing:
> "experiments": [ "use_staged_dataflow_worker_jar", "use_fastavro", "runner_harness_container_image=gcr.io/cloud-dataflow/v1beta3/harness:2.17.0", "use_multiple_sdk_containers" ],
>
> Following container image path shows us that container is missing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)