Hi, Logan.
I guess your program used an inner process function which has closure whose
checkSerialization is true (actually, this is a setting of most functions).
When a closure object is created in Flink, it may hold references to other
non-serializable objects, which may cause serialization error
Hi, Peng.
Maybe you could check your same codes in your different jars, shared
configurations between two jobs (due to your session mode).
If these are all separate, the consumer should not affect the producer from
my experience.
On Sun, Jun 11, 2023 at 10:01 AM Peng Peng wrote:
> Hi Hangxiang,
Hello,
We are using Flink 1.13.6 with Azure Kubernetes Service (AKS). Job worked fine
for many months, but right after recent upgrade of AKS to 1.25.5, taskmanager
started to get OOM killed every day. I suspected that this is maybe because AKS
1.25.x uses cgroups v2, which is not supported by JD
