Re: Transaction error in Kafka producer perf test

I understand that we could have used batch size as 0 here, if I am interpreting the documentation correctly.We essentially want no batching, and setting any value less than 256 in this particular case would achieve that, since the message size is 256 bytes for any message produced. Sincerely,

Re: Transaction error in Kafka producer perf test

We are consciously choosing the batch size in the experiment to be 1 because that is what our producer use case will need to use. Regarding the request timeout that you have mentioned, how does one set that? The command line is already passing two timeout values: ‘max.block.ms’, and

Re: Transaction error in Kafka producer perf test

Hi, Per test is based on a set of tuning parameters e.g. batch.size, axes, partitions, network latency etc. Your transactions are failing because your batch has expired, (or at least, that’s what it shows on the log). You have to tune your request timeout and batch.size correctly to improve on

Re: Transaction error in Kafka producer perf test

Anyone with a pointer on this? Do transactions work reliably with Kafka perf test tools? If yes, then is there a way to make it work in this scenario? Sincerely, Anindya Haldar Oracle Responsys > On Oct 25, 2019, at 2:51 PM, Anindya Haldar wrote: > > We are evaluating Kafka for some of our

Transaction error in Kafka producer perf test

We are evaluating Kafka for some of our use cases. As part of that effort I am trying to run an experiment with a cluster we have set up, and using the producer perf test tool supplied with the binaries. Here’s the cluster info: Runs in Kubernetes, with 4 CPUs, 32 GB RAM, 100 GB log space

Uncaught error in kafka producer I/O thread

Hello, hope you all are well, I would like to know if you guys also have seen this issue in your Apps logs: ERROR [kafka-producer-network-thread | producer-5] internals.Sender (Sender.java:240) - [Producer clientId=producer-5, transactionalId=client-XXX-1-4] Uncaught error in kafka producer I/O

Re: error in kafka producer

It means that your request has timed out or could not be sent within request timeout ms, also check max block ms. You will have to tune/increase throughout (search threads) or the timeouts. On Feb 28, 2017 2:22 PM, "shyla deshpande" wrote: >

error in kafka producer

org.apache.kafka.common.errors.TimeoutException: Expiring 1 record(s) for positionevent-6 due to 30003 ms has passed since batch creation plus linger time

RE: No error to kafka-producer on broker shutdown

AM To: users@kafka.apache.org Subject: No error to kafka-producer on broker shutdown Hi, I'm writing a little test to check Kafka high availability, with 2 brokers, 1 topic with replication factor = 2 and min.insync.replicas=2. This is the test: System.out.println("Building KafkaPro

No error to kafka-producer on broker shutdown

Hi, I'm writing a little test to check Kafka high availability, with 2 brokers, 1 topic with replication factor = 2 and min.insync.replicas=2. This is the test: System.out.println("Building KafkaProducer..."); KafkaProducer m_kafkaProducer = new

Re: Error in Kafka Producer

Thank you. It worked. lCassa On Wed, Jan 22, 2014 at 7:45 PM, Guozhang Wang wangg...@gmail.com wrote: Hello, In your case the key's type is String, not byte array, so you need to override the following property: key.serializer.class - kafka.serializer.StringEncoder Details of the

Error in Kafka Producer

Hi all, I am a new user of Kafka. I tried Java example of it and it worked great. Now when I tried to write to a Producer (Java) and send ByteArray to it as a data, I get ClassCastException as below java.lang.ClassCastException: java.lang.String cannot be cast to [B at

Re: Error in Kafka Producer

Hello, In your case the key's type is String, not byte array, so you need to override the following property: key.serializer.class - kafka.serializer.StringEncoder Details of the producer configs can be found: http://kafka.apache.org/documentation.html#producerconfigs On Wed, Jan 22, 2014 at