We're seeing an issue with our Flink TMs (1.4.2) where we explicitly set
the TM data and RPC ports. When the TM comes up, we see the following
bindings:
==================================
tcp6 0 0 :::9249 :::* LISTEN
2284/java
tcp6 0 0 10.141.34.17:6121 :::* LISTEN
2284/java
tcp6 0 0 :::6122 :::* LISTEN
2284/java
==================================
9249 is our Prometheus listener port
6121 is our data port
6122 is our RPC port
As you can see both the prometheus and rpc ports are bound to all
interfaces, but the data port is bound to a specific interface. The problem
is that it seems to be unpredictable which interface is chosen. We use
Docker, and we find that _sometimes_ the TM binds to the Docker interface,
and _sometimes_ it binds to the host interface, but only for the data port.
Is this expected? Is there any way to _force_ the TM to use a specific
interface/address?
