[
https://issues.apache.org/jira/browse/BEAM-8660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17256620#comment-17256620
]
Beam JIRA Bot commented on BEAM-8660:
-------------------------------------
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.
> 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
> Priority: P2
> Labels: portability-flink, stale-P2
> 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)
