[jira] [Resolved] (KAFKA-13865) Fix ResponseSendTimeMs metric in RequestChannel.scala was removed repeatedly

[ https://issues.apache.org/jira/browse/KAFKA-13865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13865. --- Fix Version/s: 3.3.0 Resolution: Fixed > Fix ResponseSendTimeMs metric in RequestChannel.sc

Re: [kafka-clients] Re: [VOTE] 3.2.0 RC0

Hi Guozhang, Thank you for your message! The performance regression did not find its way to the 3.2 branch. In other words, the commit that is fixed by your commit is not on branch 3.2. Best, Bruno On 27.04.22 21:36, Guozhang Wang wrote: Hi Bruno, Could I also have this commit ( https://g

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #900

See

Re: Re: [Discuss] KIP-581: Value of optional null field which has default value

Hi Cheng Pan, Thanks for raising this KIP, this would be a useful improvement! You never started a VOTE thread for this KIP. Are you interested in finishing up this work? If so, based on the discussion, I think you can open a VOTE thread as described in https://cwiki.apache.org/confluence/displa

[Discuss] KIP-832: Allow creating a producer/consumer using a producer/consumer config

Hi Bruno and frosiere, Thanks for raising this KIP, this would be a useful improvement! I advise just expose Map and Properties to the user. so that the parameters will be consistent with old one. the Advise like : 1, consumer api: public KafkaConsumer(Map configs, Des

Re: Possible Bug: kafka-reassign-partitions causing the data retention time to be reset

Hello Lqjacklee, Is there any news on this please, especially regarding my last message? Do you think it is possible to modify the segment files manually with touch -a -m -t 203801181205.09 my_sement_file? I could keep the original modification date of the files before the move and update them af

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

The current configs are hard to use for the Kafka user and a little inflexible so I am pleased to see the discussion. Ultimately we want flexibility. We don't want to force users to understand the underlying implementation/protocol and we want the producer to handle high or low throughput effic

Re: [DISCUSS] KIP-830: Allow disabling JMX Reporter

HI Federico, Thanks for taking a look. I think the method you suggest is what I included in the rejected alternatives section. The reason I rejected it is because it would force people to change their configuration in order to preserve the current behavior, hence a breaking change. Thanks, Micka

Re: [DISCUSS] KIP-830: Allow disabling JMX Reporter

Hi Mickael, I think Federico is suggesting that we would do this in AK 4.0 and hence the breaking change (with the appropriate deprecation period) would be possible. I personally prefer that option too. Is there an urgent need to do this before 4.0? Ismael On Mon, May 2, 2022 at 8:58 AM Mickael

Re: [DISCUSS] KIP-827: Expose logdirs total and usable space via Kafka API

Hi Divij, The new fields default to -1 in the protocol too. So in case a broker hits an Exception accessing a logdir and sends an error response back, the client will get -1. For this reason I think UNKNOWN_SPACE is slightly better than UNSUPPORTED. Thanks, Mickael On Fri, Apr 22, 2022 at 9:35 A

Re: [DISCUSS] KIP-660: Pluggable ReplicaPlacer

Hi, If there are no further comments, I'll start a vote in the next few days. Thanks, Mickael On Wed, Mar 30, 2022 at 3:51 AM Luke Chen wrote: > > Hi Mickael, > > Thanks for the update. > It answered my questions! > > Thank you. > Luke > > On Wed, Mar 30, 2022 at 12:09 AM Mickael Maison > wrot

Re: [DISCUSS] KIP-830: Allow disabling JMX Reporter

Hi Ismael, Thanks for the feedback. Kafka 4.0 still feels a bit far away. This is not really urgent so I guess we could wait and save us adding a new configuration setting. Thanks, Mickael On Mon, May 2, 2022 at 6:12 PM Ismael Juma wrote: > > Hi Mickael, > > I think Federico is suggesting that

[jira] [Created] (KAFKA-13866) Support more advanced time retention policies

Matthias J. Sax created KAFKA-13866: --- Summary: Support more advanced time retention policies Key: KAFKA-13866 URL: https://issues.apache.org/jira/browse/KAFKA-13866 Project: Kafka Issue Typ

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #901

See

[DISCUSS] KIP-832 Allow creating a producer/consumer using a producer/consumer config

Kip link: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211882578

Re: [DISCUSS] KIP-830: Allow disabling JMX Reporter

The other option would be to add a deprecated config that then goes away in AK 4.0. Something like "auto.include.jmx.reporter" and set it to `true` by default. In 4.0, the default would effectively switch to `false` and the config would be removed. Anyone with a config that would _change_ after thi

[jira] [Created] (KAFKA-13867) Improve JavaDoc for MetadataVersion.java

Colin McCabe created KAFKA-13867: Summary: Improve JavaDoc for MetadataVersion.java Key: KAFKA-13867 URL: https://issues.apache.org/jira/browse/KAFKA-13867 Project: Kafka Issue Type: Improvem

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #902

See

Re: Possible Bug: kafka-reassign-partitions causing the data retention time to be reset

Hi Fared, > So I guess the process applying the retention policy (log cleaner?) uses that timestamp to check whether the segment file should be deleted or not. So I ended up with a lot more data than we were supposed to store, since we are basically doubling the retention time of all the freshly m