Hello Luke,
Please look into below logs,
12:32:15.813 WARN org.apache.kafka.clients.NetworkClient - [AdminClient
clientId=test-lgn-clz-com-v0.0.43-INS_CLZ_COM-TEST_123-7e87eb30-69e9-4746-b351-beac3a085383-admin]
Error connecting to node kafka-0-0.kafka.test.svc.cluster.local:9092 (id: 0
rack: nul
Hi Vikram,
It would be good if you could share client and broker logs for troubleshooting.
Thanks.
Luke
On Wed, Dec 13, 2023 at 1:15 PM Vikram Singh
wrote:
>
> Hello,
> I have 3 node kafka cluster, when one node goes down for some reason the
> request which are serving on down node is not routi
Hello,
I have 3 node kafka cluster, when one node goes down for some reason the
request which are serving on down node is not routing to other running
node, It takes me always to restart the services,
Running on kafka version 3.2.1 (kraft mode)
On Mon, Dec 11, 2023 at 12:40 PM Luke Chen wrote:
>
Hello,
I have 3 node kafka cluster, when one node goes down for some reason the
request which are serving on down node is not routing to other running
node, It takes me always to restart the services,
Running on kafka version 3.2.1 (kraft mode)
On Mon, Dec 11, 2023 at 12:33 PM Luke Chen wrote:
>
Hi all,
I'd like to solicit input from users and maintainers on a problem we've
been dealing with for source task cleanup logic.
If you'd like to pore over some Jira history, here's the primary link:
https://issues.apache.org/jira/browse/KAFKA-15090
To summarize, we accidentally introduced a bre
