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 2020/04/23 22:32:00 UTC

[jira] [Updated] (BEAM-8310) StopOnExitJobServer interrupt handler errors

     [ https://issues.apache.org/jira/browse/BEAM-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-8310:
----------------------------------
    Status: Open  (was: Triage Needed)

> 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)