ferenc-csaky opened a new pull request, #23183:
URL: https://github.com/apache/flink/pull/23183
## What is the purpose of the change
Adds port range support for `taskmanager.data.bind-port`, which can be
helpful in a restrictive network setup.
## Brief change log
- Changed `taskmanager.data.bind-port` opion type from `Integer` to `String`.
- Introduced `PortRange` utility to be able to carry the port range string
and its generated iterator together.
- Updated `NettyConfig` to handle a `PortRange` instead of a `port` as the
port of the server.
- Updated `NettyServer` to be able to initialize itself from a `PortRange`.
- Adapted relevant code pieces and documentation.
## Verifying this change
This change added tests and can be verified as follows:
- Added `NettyServerFromPortRangeTest` to test Netty server init from a port
range.
- Manually verified by setting `taskmanager.data.bind-port` to a port range
(e.g. 55000-55100) while `taskmanager.data.port` is set to `0`, then TM should
bind to the first available port from the given range both locally and
externally.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
