[jira] [Updated] (FLINK-32949) Allow specifying the ServerSocket port for the collect function when accessing the TaskManager from the client.

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-32949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-32949:
-----------------------------------
    Labels: pull-request-available  (was: )

> Allow specifying the ServerSocket port for the collect function when accessing the TaskManager from the client.
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-32949
>                 URL: https://issues.apache.org/jira/browse/FLINK-32949
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / Core, API / DataStream, Runtime / Configuration
>            Reporter: JiaJian He
>            Assignee: Jing Ge
>            Priority: Minor
>              Labels: pull-request-available
>
> In the context of [#12069|https://github.com/apache/flink/pull/12069], the initialization of the {{CollectSinkFunction$ServerThread}} currently uses port 0, which corresponds to a random port assignment.
> Issues might arise under the following circumstances:
>  # When the JobManager and TaskManager are deployed on different servers.
>  # When network communication between servers requires specific ports to be open.
>  # When using {{sql-client.sh}} at the JobManager to execute operations like selecting data, the CollectSinkFunction$ServerThread running on the TaskManager using a random port can lead to data retrieval failures.
> The purpose of this pull request is to address this problem by introducing a configuration parameter, 'taskmanager.collect.port', which allows specifying the port for the {{{}CollectSinkFunction$ServerThread{}}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)