[GitHub] [beam] damccorm opened a new issue, #21597: Portable runner does not return job exit status to client after long-running job

[GitBox <gi...@apache.org>]

damccorm opened a new issue, #21597:
URL: https://github.com/apache/beam/issues/21597

   I submit Python Beam jobs to our Flink cluster with the PortableRunner through a remote job server. If a job finishes within a few seconds or minutes, the return status (including a dump of any Python exceptions in case there was an error) is returned to the client upon completion.
   
   If the job, however, runs for longer (say) hours, then the client and job server seem to lose connection. This results in the client hanging forever until I press Ctrl****C to terminate it, even long after the actual job has completed (which has no effect whatsoever on the actual job).
   
   Example pseudo job:
   ```
   
   print('Job started')
   with beam.Pipeline() as pipeline:
       pipeline | DoSomething()
   print('Job finished')
   ```
   
   If the pipeline finishes quickly, it looks like this from the client's perspective:
   ```
   
   $ python3 myjob.py
   Job started
   Job finished
   $ _
   ```
   
   If the job runs for longer, then the `with` statement never finishes and I have to abort the Python script with Ctrl****C:
   ```
   
   $ python3 myjob.py
   Job started
   ^C
   $ _
   ```
   
   
   Imported from Jira [BEAM-14080](https://issues.apache.org/jira/browse/BEAM-14080). Original Jira may contain additional context.
   Reported by: phoerious.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org