It uses aligned checkpoint by default in Flink which needs to process
all the data buffered in the pipeline(network and operators) during
checkpointing. In your use case, as the process speed is very slow and
so it may take too long to process the buffered data. You could try to
enable unalign chec
Hello,
I tried the configuration you mentioned, but it doesn't seem to work. Still,
thank you for your response!
At 2025-05-13 17:54:03, "Sharath" wrote:
>Hello,
>
>Have you tried enabling the buffer debloating feature to improve checkpoint
>times? Refer taskmanager.network.memor
Hello,
I tried the configuration you mentioned, but it doesn't seem to work. Still,
thank you for your response!
At 2025-05-13 17:54:03, "Sharath" wrote:
>Hello,
>
>Have you tried enabling the buffer debloating feature to improve checkpoint
>times? Refer taskmanager.network.memor
Hello,
Have you tried enabling the buffer debloating feature to improve checkpoint
times? Refer taskmanager.network.memory.buffer-debloat.enabled in
https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/
Regards,
Sharath
On Tue, May 13, 2025 at 1:59 AM 张河川 wrote:
> Hi Fli
Hi Flink community,
I’m encountering an issue with PyFlink where a FlatMap operator invokes an
external service (using a PyTorch model to generate embedding vectors). The
operator processes data very slowly, leading to an extremely long initial
checkpoint start delay, which eventually causes ch
Hi Flink community,
I’m encountering an issue with PyFlink where a FlatMap operator invokes an
external service (using a PyTorch model to generate embedding vectors). The
operator processes data very slowly, leading to an extremely long initial
checkpoint start delay, which eventually causes ch
