Hello Team,
I would like to bring attention to a potential bug regarding Kubernetes HA
in Flink 1.15.
In our implementation, we utilize the TRAP command in our entrypoint script
to perform cleanup tasks based on the exit code of the Jobmanager. However,
we have observed an issue where, when using
Hi Team,
We hit an issue after we upgrade our job from Flink 1.12 to 1.15, there's
a consistent akka.remote.OversizedPayloadException after job restarts:
Transient association error (association remains live)
akka.remote.OversizedPayloadException: Discarding oversized payload sent to
Actor[akka.
eactive mode doesn't support standby taskmanagers. As you said it
>> always uses all available resources in the cluster.
>>
>> I can see it being useful though to not always scale to MAX but (MAX -
>> some_offset).
>>
>> I'd suggest to file a
Hi Flink community,
We are trying to use Flink’s reactive mode with Kubernetes HPA for autoscaling,
however since the reactive mode will always use all available resources, it
causes a problem when we need standby task managers for fast failure recover:
The job will always use these extra stand
