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

See

[jira] [Created] (KAFKA-17584) Changing dynamic configurations resets retention

Christo Lolov created KAFKA-17584: - Summary: Changing dynamic configurations resets retention Key: KAFKA-17584 URL: https://issues.apache.org/jira/browse/KAFKA-17584 Project: Kafka Issue Type

Re: New release branch 3.9

Hello, I have filed https://issues.apache.org/jira/browse/KAFKA-17584 as a blocker. While it has not been introduced by a KIP, I think this has durability implications and needs to be addressed immediately. Let me know if you disagree! Best, Christo On Thu, 19 Sept 2024 at 16:01, José Armando G

[jira] [Resolved] (KAFKA-17579) Dynamic LogCleaner configurations are not picked up upon restart

[ https://issues.apache.org/jira/browse/KAFKA-17579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christo Lolov resolved KAFKA-17579. --- Resolution: Fixed > Dynamic LogCleaner configurations are not picked up upon restart > -

Re: [DISCUSS] KIP-1082: Enable ID Generation for Clients over the ConsumerGroupHeartbeat RPC

> This part is not clear either. It basically says that if a member joins with > an existing member id but a different epoch, it will be fenced. Then it must > rejoin with the same member id and epoch zero. This is already the current > behavior and it does not help with detecting duplicates, ri

[jira] [Created] (KAFKA-17585) `offsetResetStrategyTimestamp` should return `long` instead of `Long`

Chia-Ping Tsai created KAFKA-17585: -- Summary: `offsetResetStrategyTimestamp` should return `long` instead of `Long` Key: KAFKA-17585 URL: https://issues.apache.org/jira/browse/KAFKA-17585 Project: Ka

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

See

Re: [VOTE] KIP-1074: Allow the replication of user internal topics

Hi All, Thank you so much for the votes so far! We're just one vote away from reaching our goal for the KIP. I’d really appreciate it if you could take a moment to vote or share your thoughts! Thanks, Patrik On Mon, Sep 9, 2024 at 4:20 PM Chris Egerton wrote: > Hi Patrik, > > Sorry for the del

Re: [DISCUSS] Apache Kafka 3.8.1 release

+1 Luke Chen 於 2024年9月20日 週五 下午4:22寫道： > Thanks Josep! > +1 > > Luke > > On Fri, Sep 20, 2024 at 3:36 PM Josep Prat > wrote: > > > Hey folks, > > > > I'd like to volunteer to be the release manager for a bug fix release of > > the 3.8 series. This will be the first bug fix release and will be >

Re: [DISCUSS] KIP-1073 Return inactive observer nodes in DescribeQuorum response

Hi everyone, Thanks for reviewing the KIP again! I have updated it to address the latest comments from Colin and Jose. Going back to Jose's earlier comment here: > Did you consider making "includeFencedBroker" field value implicitly based on the DescribeClusterRequest version and the EndpointType

[DISCUSS] Apache Kafka 3.8.1 release

Hey folks, I'd like to volunteer to be the release manager for a bug fix release of the 3.8 series. This will be the first bug fix release and will be version 3.8.1. If no one has any objections, I will send out a release plan on 2024/09/23 that includes a list of all of the fixes we are targetin

Re: [DISCUSS] Apache Kafka 3.8.1 release

Thanks Josep! +1 Luke On Fri, Sep 20, 2024 at 3:36 PM Josep Prat wrote: > Hey folks, > > I'd like to volunteer to be the release manager for a bug fix release of > the 3.8 series. This will be the first bug fix release and will be version > 3.8.1. > > If no one has any objections, I will send o

Re: [DISCUSS] KIP-1082: Enable ID Generation for Clients over the ConsumerGroupHeartbeat RPC

Hi Chia-Ping, Thanks for pointing out this issue. I’m thinking that maybe we might need to define a new Exception to handle this scenario. Once the client receives this exception, it should consider the exception as a serious error and stop the process, and the user will need to assign a new memb

Re: [DISCUSS] KIP-1090 Flaky Tests 👻

Chia-Ping, I think something like that can work. I was also thinking about extracting the test names during trunk builds using Gradle and storing that somewhere. I think it's fair to say we can derive this data from Git and Develocity. We can probably figure out the implementation details later on

Re: [DISCUSS] KIP-1082: Enable ID Generation for Clients over the ConsumerGroupHeartbeat RPC

wait a minute. There is a description about fenced error in the KIP-848 > Checks whether the member epoch matches the member epoch in its current assignment. FENCED_MEMBER_EPOCH is returned otherwise. The member is also removed from the group. I failed to find the code of implementing "The member

[jira] [Resolved] (KAFKA-16813) Add global timeout for "@Test" and "@TestTemplate"

[ https://issues.apache.org/jira/browse/KAFKA-16813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-16813. Fix Version/s: 4.0.0 Resolution: Fixed > Add global timeout for "@Test" and "@TestT

[jira] [Created] (KAFKA-17587) Move test infrastructure out of core

David Arthur created KAFKA-17587: Summary: Move test infrastructure out of core Key: KAFKA-17587 URL: https://issues.apache.org/jira/browse/KAFKA-17587 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-17567) Remove TestTruncate

[ https://issues.apache.org/jira/browse/KAFKA-17567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17567. Fix Version/s: 4.0.0 Resolution: Fixed > Remove TestTruncate > ---

[jira] [Created] (KAFKA-17589) Move JUnit extensions to test-common module

David Arthur created KAFKA-17589: Summary: Move JUnit extensions to test-common module Key: KAFKA-17589 URL: https://issues.apache.org/jira/browse/KAFKA-17589 Project: Kafka Issue Type: Sub-t

[jira] [Created] (KAFKA-17588) Remove internal classes from ClusterInstance

David Arthur created KAFKA-17588: Summary: Remove internal classes from ClusterInstance Key: KAFKA-17588 URL: https://issues.apache.org/jira/browse/KAFKA-17588 Project: Kafka Issue Type: Sub-

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

See

Re: [DISCUSS] KIP-1073 Return inactive observer nodes in DescribeQuorum response

Thanks for the updates. The latest KIP LGTM. On Fri, Sep 20, 2024 at 8:38 AM Gantigmaa Selenge wrote: > > Hi everyone, > > Thanks for reviewing the KIP again! I have updated it to address the latest > comments from Colin and Jose. > > Going back to Jose's earlier comment here: > > Did you conside

Re: [DISCUSS] KIP-1090 Flaky Tests 👻

Thanks for the proposal David. Can modules opt out of this feature? For example, the raft module doesn't have any integration tests and all of the tests are meant to be deterministic. It would be dangerous to the protocol's correctness and the consistency of the cluster metadata to allow contribut

[jira] [Created] (KAFKA-17583) kafka-config script cannot set `cleanup.policy=delete,compact`

Luke Chen created KAFKA-17583: - Summary: kafka-config script cannot set `cleanup.policy=delete,compact` Key: KAFKA-17583 URL: https://issues.apache.org/jira/browse/KAFKA-17583 Project: Kafka Iss

[jira] [Created] (KAFKA-17586) AsyncKafkaConsumer#seek should NOT wait the completion of backgound

Chia-Ping Tsai created KAFKA-17586: -- Summary: AsyncKafkaConsumer#seek should NOT wait the completion of backgound Key: KAFKA-17586 URL: https://issues.apache.org/jira/browse/KAFKA-17586 Project: Kafk

[jira] [Resolved] (KAFKA-17307) Remove junit-platform.properties from test JARs

[ https://issues.apache.org/jira/browse/KAFKA-17307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Arthur resolved KAFKA-17307. -- Resolution: Duplicate > Remove junit-platform.properties from test JARs >

Re: [DISCUSS] KIP-1090 Flaky Tests 👻

> Can modules opt out of this feature? For example, the raft module doesn't have any integration tests and all of the tests are meant to be deterministic. It would be dangerous to the protocol's correctness and the consistency of the cluster metadata to allow contributors to mark tests as flaky in

Re: [DISCUSS] KIP-1090 Flaky Tests 👻

José, By default, unit tests will not be eligible for the automatic new test quarantine. Like you said, if a unit test fails, it indicates a problem. Perhaps we could auto-fail a test marked as "flaky" that is not also tagged as "integration"? Chia-Ping, >IMHO, the rule should be "unit test s