Thank you for the suggestion. I am able to identify the issue. The delay is
caused by the combination of my sink and the managed memory allocation.
On Tue, Jun 24, 2025 at 4:52 AM Xuyang wrote:
> Hi, Siva.
>
> Additionally, you can temporarily set the Flink configuration
> `pipeline.operator-ch
Hi, Siva.
Additionally, you can temporarily set the Flink configuration
`pipeline.operator-chaining: false` to unchain all operators. This will allow
you to see if one specific operator is particularly busy, which could cause
backpressure for all of its inputs.
--
Best！
Xuyang
Hi Siva,
Unfortunately the picture attached does not render for me. Would you be
able to send the output of what an `EXPLAIN` statement reveals as your
logical plan? This is a good first step to getting an idea of what each
operator is doing.
Degraded performance over time/after processing many r
Hello,
I'm new to Flink and doing a POC. I have a Flink job which reads events
from a kafka source Topic, performs some calculations and outputs a couple
of SQL sinks.
I deployed this to a stand alone cluster running on my linux virtual
machine (all default settings).
Parallelism=3
NoOfTaskSlots a
