beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henning Rohde (JIRA)" <>
Subject [jira] [Resolved] (BEAM-4635) Dataflow runner deletes the binary specified in flag --worker_binary
Date Thu, 28 Jun 2018 07:58:00 GMT


Henning Rohde resolved BEAM-4635.
       Resolution: Fixed
    Fix Version/s: 2.6.0

[~exm] Fixed the deletion bug and added auto-detection to use the running binary if already
linux-amd64. Let me know if this works for you.

> Dataflow runner deletes the binary specified in flag --worker_binary
> --------------------------------------------------------------------
>                 Key: BEAM-4635
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-go
>            Reporter: Eduardo Morales
>            Assignee: Henning Rohde
>            Priority: Minor
>             Fix For: 2.6.0
>          Time Spent: 50m
>  Remaining Estimate: 0h
> Currently a binary compiled for the dataflow runner compiles the source code again in
order to produce a worker binary.  In a production environment I will not have the source
code around so I need to provide the worker binary myself.
> The good news: there is a flag for that.
> The bad news: the dataflow runner deletes the binary after launching the pipeline.
> Expected behaviour: don't delete the binary. *I am* the owner of the worker binary. It
is *not* a temporary artifact. I would like to reuse the same binary to launch multiple dataflow
> Better yet, maybe add a flag "–self_worker_binary", so the currently running binary
is used as the worker binary. This way I don't have to copy my binary *twice* into the docker
image (once as the entrypoint, and once as data for the command line flag).

This message was sent by Atlassian JIRA

View raw message