Hi Kamal, It’s okay if you don’t mind the data order.
But it’s not very commonly seen to accept client sockets from Flink jobs, as the socket server address is dynamic and requires service discovery. Would you like to share more about the background? Best, Paul Lam > 2023年8月3日 10:26，Kamal Mittal via user <user@flink.apache.org> 写道： > > Hello Community, > > Please share views for the below mail. > > Rgds, > Kamal > > From: Kamal Mittal via user <user@flink.apache.org> > Sent: 02 August 2023 08:19 AM > To: user@flink.apache.org > Subject: Flink operator task opens threads internally > > Hello Community, > > I have a operator pipeline like as below, is it ok if “source” task opens > threads by using java thread pool and parallelize the work? > > This is needed for accepting multiple client socket connections in “single > custom source server socket function”. > > Single Custom source server socket function – ServerSocket serversocket = new > ServerSocket(9999); > Now using thread pool accept multiple connections in separate threads = new > Runnable () -> serversocket.accept(); > > > <image001.png> > > Rgds, > Kamal
