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 2020/10/24 17:10:02 UTC

[jira] [Commented] (BEAM-8660) Override returned artifact staging endpoint

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

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

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> Override returned artifact staging endpoint
> -------------------------------------------
>
>                 Key: BEAM-8660
>                 URL: https://issues.apache.org/jira/browse/BEAM-8660
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-flink
>            Reporter: Kyle Weaver
>            Assignee: Sam Bourne
>            Priority: P2
>              Labels: portability-flink, stale-assigned
>          Time Spent: 4.5h
>  Remaining Estimate: 0h
>
> When running Beam Python pipelines on Flink/Spark/etc, we connect the SDK to the job server using the job_endpoint option. The job server then returns the address of the artifact staging endpoint to the SDK.
> This is problematic when running the job server in network environments where the job server is not aware of its external hostname, for example Kubernetes. In this case, the job server will return something like localhost:8098, which might not be correct. While we do have a --job-host option, this is used both internally and externally, and the internal and external host names may not be the same.
> One solution would be to configure two separate host names in the job server. However I do not prefer this option because of the complexity it adds.
> The more straightforward solution is to add an option to Python that overrides the artifact staging endpoint returned by the server.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)