You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "ming li (Jira)" <ji...@apache.org> on 2019/10/22 04:00:11 UTC
[jira] [Created] (FLINK-14481) Modify the Flink valid socket port
check to 0 to 65535.
ming li created FLINK-14481:
-------------------------------
Summary: Modify the Flink valid socket port check to 0 to 65535.
Key: FLINK-14481
URL: https://issues.apache.org/jira/browse/FLINK-14481
Project: Flink
Issue Type: Improvement
Components: Runtime / Network
Reporter: ming li
In Flink, I found that Flink's socket port check is 'port >= 0 && port <= 65536.
{code:java}
checkArgument(serverPort >= 0 && serverPort <= 65536, "Invalid port number.");{code}
But in the process of binding the port, the valid port is 0 to 65535(A port number of zero will let the System pick up anephemeral port in a bin operation). Although the 65536 port will fail due to the port out of range when actually binding, Flink has already done a valid range check on the port, which seems to be very confusing. Should we modify Flink's port check to 0 to 65535?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)