[
https://issues.apache.org/jira/browse/BEAM-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Weaver updated BEAM-8310:
------------------------------
Description:
When I cancelled a job using FlinkRunner, I got the error: `TypeError: stop()
takes exactly 1 argument (3 given)` which is an error with this line:
[https://github.com/apache/beam/blob/c5f43342f914fc8ff367b86fb9294c38436ed3ce/sdks/python/apache_beam/runners/portability/job_server.py#L87]
However, it appears the job server was closed successfully, presumably on exit.
Which raises the question, why do we attempt to handle interrupts at all?
was:
When I cancelled a job using FlinkRunner, I got the error: `TypeError: stop()
takes exactly 1 argument (3 given)`
However, it appears the job server was closed successfully, presumably on exit.
Which raises the question, why do we attempt to handle interrupts at all?
> StopOnExitJobServer interrupt handler errors
> --------------------------------------------
>
> Key: BEAM-8310
> URL: https://issues.apache.org/jira/browse/BEAM-8310
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-harness
> Reporter: Kyle Weaver
> Priority: Major
>
> When I cancelled a job using FlinkRunner, I got the error: `TypeError: stop()
> takes exactly 1 argument (3 given)` which is an error with this line:
> [https://github.com/apache/beam/blob/c5f43342f914fc8ff367b86fb9294c38436ed3ce/sdks/python/apache_beam/runners/portability/job_server.py#L87]
> However, it appears the job server was closed successfully, presumably on
> exit. Which raises the question, why do we attempt to handle interrupts at
> all?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
