Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
1.9.1
Description
In Flink, I found that Flink's socket port check is 'port >= 0 && port <= 65536.
checkArgument(serverPort >= 0 && serverPort <= 65536, "Invalid port number.");
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?
