Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-8310

StopOnExitJobServer interrupt handler errors

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Triage Needed
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: sdk-py-harness
    • Labels:
      None

      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?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ibzib Kyle Weaver
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: