At this point I would suggest to file a ticket; these are the options
that _should_ control the behavior but apparently aren't in all cases.
On 08/12/2019 12:23, Andrea Cardaci wrote:
Hi,
Flink (or some of its services) listens on three random TCP ports
during the local[1] execution, e.g., 39951, 41009 and 42849.
[1]:
https://ci.apache.org/projects/flink/flink-docs-stable/dev/local_execution.html#local-environment
The sockets listens on `0.0.0.0` and since I need to run some
long-running tests on an Internet-facing machine I was wondering how
to make them listen on `localhost` instead or if there is anything
else I can do to improve the security in this scenario.
Here's what I tried (with little luck):
Configuration config = new Configuration();
config.setString("taskmanager.host", "127.0.0.1");
config.setString("rest.bind-address", "127.0.0.1"); // OK
config.setString("jobmanager.rpc.address", "127.0.0.1");
StreamExecutionEnvironment env =
StreamExecutionEnvironment.createLocalEnvironment(StreamExecutionEnvironment.getDefaultLocalParallelism(),
config);
Only the `rest.bind-address` configuration actually changes the
binding address of one of those ports. Are there other parameters that
I'm not aware of or this is not the right approach in local mode?
Best,
Andrea
