Re: We found a deadlock problem when a single piece of data is too large on Flink1.13.2, do not continue to process the data, which more understand the data transmission piece, welcome to comment.

The process stack is as follows： "Map (1/10)#4" #346 prio=5 os_prio=0 tid=0x023e9800 nid=0x5a7f waiting on condition [0x7fc291fd8000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x00079c54dce8> (a java.util.concurrent.

Re: Stopping the flink 1.18 program with savepoint seems to fail with timeout

Hi, In the background it is a REST call to Flink. If it takes too long to create the savepoint, you might hit a timeout. You can increase this using the configuration client.timeout [1]. You can also use the --detached option for the stop action, which will return once it receives a trigger ID fro