Hello,
I experienced
CoordinatorNotAvailableException in my flink jobs after our kafka supplier
(aiven) did a maintenance update of the cluster. This update is performed
by starting up new kafka nodes, copying over data, and switching over
internally. The flink jobs runs as expected,  with the only issue that they
are unsuccessful in committing group offsets.

Restarting the job from checkpoint/savepoint resolves the issue, but I
would rather not restart all jobs after every kafka maintenance update.

Any ideas ?

Kind regards,
Lars Skjærven

Reply via email to