[
https://issues.apache.org/jira/browse/FLINK-35332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18041388#comment-18041388
]
Gabor Somogyi commented on FLINK-35332:
---------------------------------------
[{{aac57b8}}|https://github.com/apache/flink/commit/aac57b8f154842b64bff73b7bdea66f7c00197f8]
on release-1.20
> Manually setting rest.bind-address does not work for Flink running on Hadoop
> Yarn dual network environment
> ----------------------------------------------------------------------------------------------------------
>
> Key: FLINK-35332
> URL: https://issues.apache.org/jira/browse/FLINK-35332
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
> Affects Versions: 1.20.0, 1.19.1, 2.0-preview
> Reporter: Yao Zhang
> Assignee: Yao Zhang
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.0.0, 1.20.4
>
>
> Given the Hadoop Yarn cluster with dual networks:
> * 192.168.x.x: For data transfer. Speed: 10Gbps.
> * 10.x.x.x: For management only. Speed: 1Gbps.
>
> A client outside the Hadoop Yarn cluster is configured, with management
> network only(10.x.x.x) and data transfer high speed network not accessible.
> To reproduce, we sumbit a Flink job from this client(Batch word count for
> example), the job can be successfully submitted but the result cannot be
> retrieved, with the exception: Connection refused:
> \{jobmanager_hostname}:\{jm_port}. The root cause is the job manager rest
> address is bind to its actual address (192.168.x.x) rather than 0.0.0.0.
> Manually setting rest.bind-address does not work.
>
> One of the changes in Flink-24474 in YarnEntrypointUtils overwrites
> RestOptions.BIND_ADDRESS to the node's actual address. This change should be
> reverted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
