You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2022/03/20 17:26:00 UTC

[jira] [Commented] (BEAM-12580) Add ability to specify gRPC server/worker ports

    [ https://issues.apache.org/jira/browse/BEAM-12580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509481#comment-17509481 ] 

Beam JIRA Bot commented on BEAM-12580:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Add ability to specify gRPC server/worker ports
> -----------------------------------------------
>
>                 Key: BEAM-12580
>                 URL: https://issues.apache.org/jira/browse/BEAM-12580
>             Project: Beam
>          Issue Type: Improvement
>          Components: beam-model, runner-universal
>    Affects Versions: 2.30.0
>         Environment: Python Linux
>            Reporter: Marie Hoeger
>            Priority: P2
>              Labels: stale-P2
>
> My development setup is all Docker-based and I work inside a Docker container for development. From this docker environment, i'd love to be able to [run a pipeline with a custom container image|https://beam.apache.org/documentation/runtime/environments/] for local testing. I've been able to launch a sister beam docker container from my main docker container, but am running into an issue with the ports.
> It would be really helpful if I could set a value for the control_address and logging_endpoint of the GrpcServer for the portable runner worker.
> The 'docker run' command passes in a control_address [here|https://github.com/apache/beam/blob/2aab1b04c2f5002527e0f2d25075b282feb7c054/sdks/python/apache_beam/runners/portability/fn_api_runner/worker_handlers.py#L767-L769] which ultimately comes from [here.|https://github.com/apache/beam/blob/2aab1b04c2f5002527e0f2d25075b282feb7c054/sdks/python/apache_beam/runners/portability/fn_api_runner/worker_handlers.py#L464] Similarly, the logging_endpoint passed in  [here|https://github.com/apache/beam/blob/2aab1b04c2f5002527e0f2d25075b282feb7c054/sdks/python/apache_beam/runners/portability/fn_api_runner/worker_handlers.py#L766] comes from [here|https://github.com/apache/beam/blob/2aab1b04c2f5002527e0f2d25075b282feb7c054/sdks/python/apache_beam/runners/portability/fn_api_runner/worker_handlers.py#L515].
> This would be a pretty small change, just exposing some knob to configure those endpoints rather than having them chosen by the gRPC server. Thanks!!



--
This message was sent by Atlassian Jira
(v8.20.1#820001)