[jira] [Created] (KAFKA-18841) Enable to test docker image locally

Chia-Ping Tsai created KAFKA-18841: -- Summary: Enable to test docker image locally Key: KAFKA-18841 URL: https://issues.apache.org/jira/browse/KAFKA-18841 Project: Kafka Issue Type: Improveme

RE: [DISCUSS] KIP-1121: Compression acceleration in Kafka

Hi Greg, Thanks for your response. 1. Some changes will be made to the Compression and Builder interfaces. At least one default method, isAvailable(), would be added to the Builder interface. The static methods in the Compression interface that create and return specific builders would be modif

[jira] [Resolved] (KAFKA-18831) Migrating to log4j2 introduce behavior changes of adjusting level dynamically

[ https://issues.apache.org/jira/browse/KAFKA-18831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18831. Resolution: Fixed trunk: https://github.com/apache/kafka/commit/d31cbf59dee6a77c1c673db06

[jira] [Created] (KAFKA-18844) Fix flaky QuorumControllerTest.testBalancePartitionLeaders()

David Jacot created KAFKA-18844: --- Summary: Fix flaky QuorumControllerTest.testBalancePartitionLeaders() Key: KAFKA-18844 URL: https://issues.apache.org/jira/browse/KAFKA-18844 Project: Kafka I

Re: [DISCUSS] Change log.segment.bytes config type from int to long

Guys, any thoughts on that? Please let me know! On Thu, 13 Feb 2025 at 22:31, Mikhail Fesenko wrote: > Hi everyone, > > I’d like to propose a change the data type of log.segment.bytes from int > to long, allowing segment sizes beyond the current 2GB limit. > > Rationale: > > Currently, the maxim

Re: [DISCUSS] Change log.segment.bytes config type from int to long

hi Mikhail > So Increasing the limit to 3–4GB (or more) would better align with today’s storage capabilities. Out of curiosity, what is the benefit of using the larger segment? While changing the type from int to long is a minor change, allowing or encouraging users to create large segments requi

Re: Simplifying Java import order tooling

Nothing is "wrong with it" -- it's a little esoteric and very tied to the Spotless tool as custom written software. (https://github.com/diffplug/spotless/blob/main/lib/src/main/java/com/diffplug/spotless/java/ImportSorter.java) My discussion is centered around eventual migration to probably tree-w

[jira] [Created] (KAFKA-18847) Refactor OAuth layer to improve reusability

Kirk True created KAFKA-18847: - Summary: Refactor OAuth layer to improve reusability Key: KAFKA-18847 URL: https://issues.apache.org/jira/browse/KAFKA-18847 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-18795) Remove Records#downConvert

[ https://issues.apache.org/jira/browse/KAFKA-18795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18795. Resolution: Fixed > Remove Records#downConvert > -- > >

kafka producer exception due to TimeoutException:

Hi all iam encountering a TimeoutException while publishing messages to Kafka during load testing of our Kafka producer. The error message indicates that records are expiring before they can be sent successfully: org.apache.kafka.common.errors.TimeoutException: Expiring 115 record(s) for ORG_LT

Re: [DISCUSS] Change log.segment.bytes config type from int to long

Hi, Mikhail, Currently, the index file uses 4 bytes to represent the file position of a record batch within a segment file. This is based on the assumption that each segment is capped at 2GB. RemoteLogSegmentMetadata is a public interface and currently uses int to represent segmentSizeInBytes. If

Re: [DISCUSS] KIP-1134: Virtual Clusters in Kafka

Hey Daniel and Viktor, Thanks so much for your answers! 1. > The issue we encountered here is how can clients inside a VC can > refer to topics linked in nested VCs? An admin of a VC needs a way to refer > to the resources inside the VC and the child VCs. I would think the only operations referr

[jira] [Resolved] (KAFKA-18534) docker build fail because log4j

[ https://issues.apache.org/jira/browse/KAFKA-18534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18534. Resolution: Duplicate see KAFKA-18340 > docker build fail because log4j > ---

[jira] [Resolved] (KAFKA-18737) KafkaDockerWrapper setup functions fails due to storage format command

[ https://issues.apache.org/jira/browse/KAFKA-18737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18737. Resolution: Fixed trunk: https://github.com/apache/kafka/commit/767a62ade605a1c133d35f676

[jira] [Resolved] (KAFKA-18033) ShareConsumerTest is flaky

[ https://issues.apache.org/jira/browse/KAFKA-18033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-18033. -- Resolution: Fixed > ShareConsumerTest is flaky > -- > >

[jira] [Created] (KAFKA-18843) MirrorMaker2 workerId is not unique, but use the same for all the workers

Bertalan Kondrat created KAFKA-18843: Summary: MirrorMaker2 workerId is not unique, but use the same for all the workers Key: KAFKA-18843 URL: https://issues.apache.org/jira/browse/KAFKA-18843 Pro

[jira] [Resolved] (KAFKA-17611) Remove ZK from Kafka 4.0

[ https://issues.apache.org/jira/browse/KAFKA-17611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-17611. - Resolution: Fixed > Remove ZK from Kafka 4.0 > > > Key:

[jira] [Created] (KAFKA-18845) Fail test QuorumControllerTest#testUncleanShutdownBrokerElrEnabled

黃竣陽 created KAFKA-18845: --- Summary: Fail test QuorumControllerTest#testUncleanShutdownBrokerElrEnabled Key: KAFKA-18845 URL: https://issues.apache.org/jira/browse/KAFKA-18845 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-18846) Flaky test QuorumControllerTest#testMinIsrUpdateWithElr

黃竣陽 created KAFKA-18846: --- Summary: Flaky test QuorumControllerTest#testMinIsrUpdateWithElr Key: KAFKA-18846 URL: https://issues.apache.org/jira/browse/KAFKA-18846 Project: Kafka Issue Type: Test

Re: [DISCUSS] KIP-1133: AK Documentation and Website in Markdown

Thanks for the KIP, Harish! I am +100 just on the title alone :) The motivations in the KIP are sound. All of these are very real annoyances when it comes to maintaining our docs. I suspect we have not done anything to improve them since the system we have worked well enough in the past. A better

[jira] [Created] (KAFKA-18842) Connector maximum allowed number

Jarkko Jaakola created KAFKA-18842: -- Summary: Connector maximum allowed number Key: KAFKA-18842 URL: https://issues.apache.org/jira/browse/KAFKA-18842 Project: Kafka Issue Type: Improvement

Re: [DISCUSS] KIP-1134: Virtual Clusters in Kafka

Hi Greg, Replying to the rest of your points: 3. Well, after thinking about it a lot, I think that overall it would complicate the feature without adding much usefulness. If we assume that a topic is inside a directory hierarchy, then it wouldn't be transparent anymore to users. Right now we say

[jira] [Resolved] (KAFKA-18840) Add system test for 2-rolling-bounce bridge release upgrade path in Streams

[ https://issues.apache.org/jira/browse/KAFKA-18840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman resolved KAFKA-18840. Resolution: Invalid Closing this as invalid – after further inspection it

Build failed in Jenkins: Kafka » kafka-2.7-jdk8 #200

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on builds30 (ubuntu) in workspace

Re: [DISCUSS] KIP-1124: Providing a clear Kafka Client upgrade path

whew, long response from Matthias :P Lot to digest but I want to add on/respond to a few points: If they want to be "advantageous", they could make it a two step upgrade > I guess, and go from 2.5 (or older) directly to 3.x and apply all > required code changes in a single upgrade step, and repea