Thank you, Yang:
We have found the root cause.
In the logic of Flink operator, it calls Flink's rest API to stop this
job then calls the K8s's API to stop the deployment of Flink jobManager.
However it took more than one minute for K8s to delete that deployment, so when
the JM's mai
Hello,
We have noticed that when we add a *new kafka sink* operator to the graph, *and
start from the last save point*, the operator is 100% busy for several
minutes and *even 1/2-1 hour* !!!
The problematic code seems to be the following for-loop in
getTransactionalProducer() method:
*org.apach
