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 2020/11/01 17:11:01 UTC
[jira] [Commented] (BEAM-11000) NullPointerException in Flink
manager when submitting job
[ https://issues.apache.org/jira/browse/BEAM-11000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224285#comment-17224285 ]
Beam JIRA Bot commented on BEAM-11000:
--------------------------------------
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.
> NullPointerException in Flink manager when submitting job
> ---------------------------------------------------------
>
> Key: BEAM-11000
> URL: https://issues.apache.org/jira/browse/BEAM-11000
> Project: Beam
> Issue Type: Bug
> Components: beam-community
> Affects Versions: 2.24.0
> Environment: jobmanager:
> image: flink:1.11.2-scala_2.11
> ports:
> - "8081:8081"
> command: jobmanager
> environment:
> - |
> FLINK_PROPERTIES=
> jobmanager.rpc.address: jobmanager
> taskmanager:
> image: flink:1.11.2-scala_2.11
> depends_on:
> - jobmanager
> command: taskmanager
> environment:
> - |
> FLINK_PROPERTIES=
> jobmanager.rpc.address: jobmanager
> taskmanager.numberOfTaskSlots: 2
> beamworker:
> image: apache/beam_python3.8_sdk
> ports:
> - "50000:50000"
> command: --worker_pool
> Reporter: Samuel Brotherton
> Assignee: Aizhamal Nurmamat kyzy
> Priority: P2
> Labels: stale-assigned
>
> Apologies if this is user error, as I am still learning Beam. I am attempting to run a python-based pipeline on the Flink runner, with Flink and an external beam image running inside docker-compose (see "Environment"). Whenever I submit a job, I get the following error. Am I doing something wrong? Thanks in advance.
> * Edit: Jira mangled the traceback, you can see it here: https://gist.github.com/sbrother/b9f62580fbab84e2cfc925e0ea8ffc07
--
This message was sent by Atlassian Jira
(v8.3.4#803005)