l 2024 at 05:16
To: users@kafka.apache.org
Subject: Re: Kraft controller readiness checks
EXTERNAL: Use caution when clicking on links or opening attachments.
Thanks Luke, this helps for our use case. It does not cover the buildout
of a new cluster where there are no brokers, but that should be re
ordered rotation imposed by
> > statefulset parallel rolling restart, together with the URP readiness
> check
> > and the PDB, we are guaranteed not to cause any problem read or write
> > errors. Rotations are rather long, but we don’t really care about speed.
> >
&g
P readiness check
> and the PDB, we are guaranteed not to cause any problem read or write
> errors. Rotations are rather long, but we don’t really care about speed.
>
> Thanks,
>
> Frank
>
> --
> Francesco Burato | Software Development Engineer | Adobe |
> bur...@adobe.
,
Frank
--
Francesco Burato | Software Development Engineer | Adobe |
bur...@adobe.com<mailto:bur...@adobe.com> | c. +44 747
9029370
From: Luke Chen
Date: Friday, 19 April 2024 at 05:21
To: users@kafka.apache.org
Subject: Re: Kraft controller readiness checks
EXTERNAL: Use cautio
Hello Frank,
That's a good question.
I think we all know there is no "correct" answer for this question. But I
can share with you what our team did for it.
Readiness: controller is listening on the controller.listener.names
The rationale behind it is:
1. The last step for the controller node
Hello,
I have a question regarding the deployment of Kafka using Kraft controllers in
a Kubernetes environment. Our current Kafka cluster is deployed on K8S clusters
as statefulsets without operators and our brokers are configured to use a
script which marks the containers as unready if
