Re: [VOTE] KIP-782: Expandable batch size in producer

Hi Artem, Thanks for the suggestion. Let me confirm my understanding is correct. So, what you suggest is that the "batch.size" is more like a "soft limit" batch size, and the "hard limit" is "batch.max.size". When reaching the batch.size of the buffer, it means the buffer is "ready" to be be sent.

Re: [DISCUSS] KIP-785: Emit Metric Client Quota Values

Hi Igor, yes sorry for the off by one and thanks for the catch! Will update and start a new discussion thread for clarity. Best, Mason On Fri, Oct 22, 2021 at 5:04 PM Igor Soarez wrote: > Hi Mason, > > Thanks for the KIP. > > There is already a KIP-785. Should this be KIP-786? > > -- > Igor >

Re: [DISCUSS] KIP-785: Emit Metric Client Quota Values

Hi Mason, Thanks for the KIP. There is already a KIP-785. Should this be KIP-786? -- Igor On Fri, Oct 22, 2021, at 9:26 PM, Mason Legere wrote: > Hi All, > > I would like to start a discussion for the following KIP - aimed at > providing some insight into when our clients are being throttled.

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #536

See Changes: -- [...truncated 495961 lines...] [2021-10-22T22:16:02.748Z] > Task :streams:testJar [2021-10-22T22:16:02.748Z] > Task :streams:testSrcJar

[DISCUSS] KIP-785: Emit Metric Client Quota Values

Hi All, I would like to start a discussion for the following KIP - aimed at providing some insight into when our clients are being throttled. KIP-785: Emit Metric Client Quota Values Best, Mason

[jira] [Created] (KAFKA-13395) Emit Client Quota Values as Metric

Mason Joseph Legere created KAFKA-13395: --- Summary: Emit Client Quota Values as Metric Key: KAFKA-13395 URL: https://issues.apache.org/jira/browse/KAFKA-13395 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-13394) Topic IDs should be removed from PartitionFetchState if they are no longer sent by the controller

Justine Olshan created KAFKA-13394: -- Summary: Topic IDs should be removed from PartitionFetchState if they are no longer sent by the controller Key: KAFKA-13394 URL:

Re: [VOTE] KIP-782: Expandable batch size in producer

Hi Luke, Nice suggestion. It should optimize how memory is used with different production rates, but I wonder if we can take this idea further and improve batching in general. Currently batch.size is used in two conditions: 1. When we append records to a batch in the accumulator, we create a

[VOTE] KIP-782: Expandable batch size in producer

Hi Kafka dev, I'd like to start a vote for the proposal: KIP-782: Expandable batch size in producer. The main purpose for this KIP is to have better memory usage in producer, and also save users from the dilemma while setting the batch size configuration. After this KIP, users can set a higher

[jira] [Resolved] (KAFKA-13381) Wrap all uncaught exceptions as StreamsException with TaskId field

[ https://issues.apache.org/jira/browse/KAFKA-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman resolved KAFKA-13381. Resolution: Fixed > Wrap all uncaught exceptions as StreamsException with