Re: what happened in case of single disk failure

Thanks Peter, it makes a lot of sense. Peter Bukowinski 于2020年3月3日周二 上午11:56写道： > Whether your brokers have a single data directory or multiple data > directories on separate disks, when a disk fails, the topic partitions > located on that disk become unavailable. What happens next depends on

Re: Issue in retention with compact,delete cleanup policy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 If I understand the issue correctly, the problem is that some data, even if it is not updated for a long period of time will, never be deleted because it's always in a segment with new data? As your segment size is already fairly small, I don't see

Re: Does the response to a OffsetFetch include non-committed transactional offsets?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 A fetch-offset request would return the latest "stable" offset, ie, either non-transactional or transactional+committed. If there is a pending transaction, the corresponding offset would not be returned. Btw: Kafka 2.5 allows you to block a

RE: Producer-Perf-test

Hi Himanshu, Pasting screenshot for better view. My Observations: * When I increased partitions, and keep replica same, then Throughput increases. Compare Row 1 and 2 * Increase number of replica and partitions same: Throughput decreased than before. Row 2 and 3 * Increase number

RE: Issue in retention with compact,delete cleanup policy

Bubbling this up to understand if anyone else are in similar use case. -Original Message- From: Koushik Chitta Sent: Sunday, February 23, 2020 1:35 PM To: users@kafka.apache.org; d...@kafka.apache.org Subject: [EXTERNAL] Issue in retention with compact,delete cleanup policy Hi, I

Re: Subject: [VOTE] 2.4.1 RC0

Hi, I ran: $ https://github.com/elalonde/kafka/blob/master/bin/verify-kafka-rc.sh 2.4.1 https://home.apache.org/~bbejeck/kafka-2.4.1-rc0 All checksums and signatures are

Re: Default values for max.request.size and message.max.bytes seem wrong

This was fixed recently: https://github.com/apache/kafka/commit/bd5a1c4d368b9e91398e48400965d30d3045062e Ismael On Tue, Mar 3, 2020 at 11:34 AM Michael Rubin wrote: > (I am re-asking my SO question: >

Default values for max.request.size and message.max.bytes seem wrong

(I am re-asking my SO question: https://stackoverflow.com/questions/60458132/default-values-for-max-request-size-and-message-max-bytes-seem-wrong ) The default value for the

Re: Producer-Perf-test

It's okay. You could probably take the screenshot and share it. On Tue, 3 Mar 2020, 20:13 sunil chaudhari, wrote: > Hi Himanshu, > Sorry but I pasted from excel. Dont know how it got messed up? > > Will resend it. > > On Tue, 3 Mar 2020 at 6:48 PM, Himanshu Shukla < >

Re: Producer-Perf-test

Hi Himanshu, Sorry but I pasted from excel. Dont know how it got messed up? Will resend it. On Tue, 3 Mar 2020 at 6:48 PM, Himanshu Shukla wrote: > could you please share the result in some proper way? Each field is line by > line. > > On Tue, Mar 3, 2020 at 2:43 PM Sunil CHAUDHARI > wrote: >

Does the response to a OffsetFetch include non-committed transactional offsets?

If a consumer sends its offset for a topic-partition as part of a transaction, and someone sends an OffsetFetch request for that consumer group and topic-partition before the transaction is committed, is the OffsetFetch response meant to include that pending offset, or only the last offset sent

SV: Error handling guarantees in Kafka Streams

Thanks, the explanation makes sense. I'll dig around a bit to see if I can figure out why that's not what I'm seeing in my testing. Best Regards Magnus Reftel -Opprinnelig melding- Fra: Bruno Cadonna Sendt: onsdag 26. februar 2020 17:57 Til: Users Emne: Re: Error handling guarantees

Re: Producer-Perf-test

could you please share the result in some proper way? Each field is line by line. On Tue, Mar 3, 2020 at 2:43 PM Sunil CHAUDHARI wrote: > Hi, > I have done performance testing of Kafka cluster using > kafka-producer-perf-test.sh > I created diff type of topics and did perf testing. Example:

Please help: How to print --reporting-interval in the perf metrics?

Hi, I want to test consumer perf using kafka-consumer-perf-test.sh I am running below command: ./kafka-consumer-perf-test.sh --broker-list localhost:9092 --topic MB3P3R --messages 65495 --num-fetch-threads 9 --print-metrics --reporting-interval 5000 --show-detailed-stats >

Producer-Perf-test

Hi, I have done performance testing of Kafka cluster using kafka-producer-perf-test.sh I created diff type of topics and did perf testing. Example: MB1P1R= MB is my topic name with 1 Partition and 1 replica. I have 3 nodes cluster. My Observations: * When I increased partitions, and keep

Producer MESSAGE_TOO_LARGE warnning when compression is zstd

Hi, Issue: The MESSAGE_TOO_LARGE warning occurred when I run producer-perf-test.sh and the broker is arm server. Below it’s the command I used: bin/kafka-topics.sh --create --bootstrap-server arm-server:9092 --replication-factor 1 --partitions 6 --topic test bin/kafka-producer-perf-test.sh