Re: Kafka Producer Record Error Rate

2022-04-04 Thread Neeraj Vaidya
Thank you David and Liam for your excellent responses. Checking in the consumer will be extremely difficult. However, I am unclear what the record-error-rate|total metric for a producer means, Does the metric get incremented only when the record could not make it to the topic or even when there

HACKING vulnerability is SpringBoot (Java) for apache kafka

2022-04-04 Thread Kafka Life
Hi Kafka Experts Regarding the recent threat of vulnerability in spring framework , CVE-2022-22965 vulnerability is SpringBoot (Java) for apache kafka and Zookeeper. Could one of you suggest how Apache kafka and zk are impacted and what should be the ideal fix for this . Vulnerability in the Spri

Re: HACKING vulnerability is SpringBoot (Java) for apache kafka

2022-04-04 Thread Luke Chen
Hi, The impact for the CVE-2022-22965? Since this is a RCE vulnerability, which means the whole system (including Kafka and ZK) is under the attackers' control, and can do whatever they want. The ideal fix for this is to upgrade Spring Framework 5.3.18 and 5.2.20 or greater. Alternatively, you ca

Re: HACKING vulnerability is SpringBoot (Java) for apache kafka

2022-04-04 Thread Kafka Life
Dear Luke , Thank you for your kind and prompt response. On Mon, Apr 4, 2022 at 1:23 PM Luke Chen wrote: > Hi, > > The impact for the CVE-2022-22965? Since this is a RCE vulnerability, which > means the whole system (including Kafka and ZK) is under the attackers' > control, and can do whatever

kafka producer exception due to TimeoutException: Expiring records for topic 120000ms has passed since batch creation

2022-04-04 Thread Pushkar Deole
Hi All, We are intermittently seeing KafkaProducerException. The nested exception is as below: org.springframework.kafka.core.KafkaProducerException: Failed to send; nested exception is org.apache.kafka.common.errors.TimeoutException: Expiring 10 record(s) for analytics.mpe.passthrough-0:12 m

Re: Kafka Producer Record Error Rate

2022-04-04 Thread Liam Clarke-Hutchinson
Hi Neeraj, However, I am unclear what the record-error-rate|total metric for a > producer means, > Does the metric get incremented only when the record could not make it to > the topic or even when there was a transient/retriable error trying to send > the message to the topic ? The latter - so

Re: Kafka Producer Record Error Rate

2022-04-04 Thread Neeraj Vaidya
Thanks Liam. Yes, I do believe the following should really help: A producer metric which shows records which did not make their way to the topic because of retries being exhausted or timeout being exhausted . If the metric is at a batch level, then we will need to work out the math to calculate

Re: Kafka Producer Record Error Rate

2022-04-04 Thread Liam Clarke-Hutchinson
Hi Neeraj, Sorry, I was wrong, the error rate is only records that failed to send after all retries were exhausted (or if retries weren't possible). So if that's gone up, then records have been dropped by the producer's sender. Cheers, Liam On Tue, 5 Apr 2022 at 10:35, Neeraj Vaidya wrote:

Re: kafka producer exception due to TimeoutException: Expiring records for topic 120000ms has passed since batch creation

2022-04-04 Thread Liam Clarke-Hutchinson
Hi Pushkar, Could be a lot of things. What's your linger.ms configured for? Cheers, Liam On Tue, 5 Apr 2022 at 05:39, Pushkar Deole wrote: > Hi All, > > We are intermittently seeing KafkaProducerException. The nested exception > is as below: > > org.springframework.kafka.core.KafkaProducerExc

Re: Request was for a topic or partition that does not exist on this broker error when using Kafka in Kraft mode

2022-04-04 Thread Francis Chuang
Not sure if this is due to the broker rebalancing multiple times every second for the topic. Relevant logs for the 3 brokers below: Broker 1: [2022-04-04 23:14:24,232] INFO Sent auto-creation request for Set(test-bounded-context-1-6cdaff21-6562-418a-92e8-1f2d8fa0c704) to the active controller.

Re: Request was for a topic or partition that does not exist on this broker error when using Kafka in Kraft mode

2022-04-04 Thread Liam Clarke-Hutchinson
Hi Francis, The rebalancing is your consumer group, it looks like your consumer is repeatedly entering and leaving when hitting that error. Do you have logs from the consumer side? Cheers, Liam On Tue, 5 Apr 2022 at 11:30, Francis Chuang wrote: > Not sure if this is due to the broker rebalanc

Re: Request was for a topic or partition that does not exist on this broker error when using Kafka in Kraft mode

2022-04-04 Thread Francis Chuang
Hi Liam, These are the logs I have for the consumer (I'll see if I can turn on debug mode for sarama to get more info): 2022-04-04T23:14:24.519ZERROR client/client.go:410Kafka consumer error{"error": "kafka: error while consuming test-bounded-context-1-6cdaff21-6562-418a-92e8

Re: Request was for a topic or partition that does not exist on this broker error when using Kafka in Kraft mode

2022-04-04 Thread Francis Chuang
Hmm, upon further investigation, the client also returns "kafka server: Request was for a topic or partition that does not exist on this broker." if I am not using a consumer group. There doesn't seem to be anything interesting in kafka's logs: Broker 1: [2022-04-04 23:58:42,480] INFO [Control

Re: kafka producer exception due to TimeoutException: Expiring records for topic 120000ms has passed since batch creation

2022-04-04 Thread Pushkar Deole
Liam, This is set to default and we have not changed these configurations. So from kafka docs, the default value of linger.ms for producer is 0 On Tue, Apr 5, 2022 at 4:42 AM Liam Clarke-Hutchinson wrote: > Hi Pushkar, > > Could be a lot of things. What's your linger.ms configured for? > > Chee