Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #79

See Changes: [github] KAFKA-10068: add task assignment performance tests (#8892) -- [...truncated 6.59 MB...] org.apache.kafka.streams.TopologyTestDriverTest

Jenkins build is back to normal : Kafka » kafka-trunk-jdk8 #78

See

[jira] [Resolved] (KAFKA-10492) Core Raft implementation

[ https://issues.apache.org/jira/browse/KAFKA-10492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-10492. - Resolution: Fixed > Core Raft implementation > > >

Jenkins build is back to normal : Kafka » kafka-trunk-jdk15 #79

See

Re: [DISCUSS] KIP-567: Kafka Cluster Audit (new discussion)

An example I had in mind was the ProduceResponse - the auditor might need access to the new end offset of the partitions. The event-based approach sounds good - new events and fields can be added on-demand. Do we need the same versioning strategy we use with the requests/responses? Daniel Viktor

Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #77

See Changes: [github] KAFKA-10459: Document IQ APIs where order does not hold between stores (#9251) -- [...truncated 3.26 MB...]

Re: [VOTE] KIP-584: Versioning scheme for features

Hi all, I wanted to let you know that I have made the following changes to the KIP-584 write up. The purpose is to ensure the design is correct for a few things which came up during implementation: 1. Per FeatureUpdate error code: The UPDATE_FEATURES controller API is no longer transactional.

Re: [DISCUSS] KIP-671: Shutdown Streams Application when appropriate exception is thrown

Walker, I am sorry, but I still have a comment on the KIP although you have already started voting. What happens when a consumer of the group skips the rebalancing that propagates the shutdown request? Do you give a guarantee that all Kafka Streams clients are shutdown or is it best effort?

Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #78

See Changes: [github] KAFKA-10459: Document IQ APIs where order does not hold between stores (#9251) -- [...truncated 3.30 MB...]

ApacheCon Bug Bash

Kafka Developers, As part of our sponsorship of ApacheCon, our company MuseDev is doing a Bug Bash for select Apache projects. We'll bring members of the ApacheCon community together to find and fix a range of security and performance bugs during the conference, and gameify the experience with

Re: ApacheCon Bug Bash

Hi Tom, I would love to participate. You can scan the AIPlatform here https://github.com/bugsbunnyshah/AIPlatform Thanks Sohil On Tue, Sep 22, 2020 at 6:11 PM Tom DuBuisson wrote: > Kafka Developers, > > > > > > > > As part of our sponsorship of ApacheCon, our company MuseDev is doing a Bug

Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #79

See Changes: [github] MINOR: Fix log message when tasks directory is cleaned manually (#9262) [github] KAFKA-10492; Core Kafka Raft Implementation (KIP-595) (#9130)

Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #80

See Changes: [github] MINOR: Fix log message when tasks directory is cleaned manually (#9262) [github] KAFKA-10492; Core Kafka Raft Implementation (KIP-595) (#9130)

Jenkins build is back to normal : Kafka » kafka-trunk-jdk11 #80

See

Jenkins build is back to normal : Kafka » kafka-2.6-jdk8 #17

See

[jira] [Created] (KAFKA-10511) Fix minor behavior difference in `MockLog`

Jason Gustafson created KAFKA-10511: --- Summary: Fix minor behavior difference in `MockLog` Key: KAFKA-10511 URL: https://issues.apache.org/jira/browse/KAFKA-10511 Project: Kafka Issue Type:

[VOTE] KIP-653: Upgrade log4j to log4j2

Hi devs, Here I open the vote for KIP-653: Upgrade log4j to log4j2. It replaces the obsolete log4j logging library into the current standard, log4j2, with maintaining backward-compatibility. Thanks, Dongjin -- *Dongjin Lee* *A hitchhiker in the mathematical world.* *github:

Re: [DISCUSS] KIP-653: Upgrade log4j to log4j2

Hi devs, I updated the KIP with the migration plan I discussed with Ismael. I think 2.7.0 is the perfect time for starting migration into log4j2. If we miss this opportunity, the migration would be much harder. So please have a look at this proposal. I also opened a voting thread for this.

Re: [DISCUSS] Apache Kafka 2.7.0 release

Boyan, Done. Thanks for the heads up. -Bill On Mon, Sep 21, 2020 at 6:36 PM Boyang Chen wrote: > Hey Bill, > > unfortunately KIP-590 will not be in 2.7 release, could you move it to > postponed KIPs? > > Best, > Boyang > > On Thu, Sep 10, 2020 at 2:41 PM Bill Bejeck wrote: > > > Hi Gary, > >

[VOTE] KIP-516: Topic Identifiers

Hi all, I'd like to call a vote on KIP-516: Topic Identifiers. Here is the KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-516%3A+Topic+Identifiers The discussion thread is here:

[jira] [Resolved] (KAFKA-10507) Limit the set of APIs returned in pre-authentication ApiVersions

[ https://issues.apache.org/jira/browse/KAFKA-10507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-10507. - Resolution: Won't Do > Limit the set of APIs returned in pre-authentication ApiVersions

[jira] [Created] (KAFKA-10512) JmxTool Can Crash on Unmarshall Error

Matthew Wong created KAFKA-10512: Summary: JmxTool Can Crash on Unmarshall Error Key: KAFKA-10512 URL: https://issues.apache.org/jira/browse/KAFKA-10512 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-630: Kafka Raft Snapshot

Hi, Jose, Thanks for the updated KIP. A few more comments below. 20. "Metadata Cache: The component that generates snapshots, reads snapshots and reads logs for observer replicas of the topic partition __cluster_metadata." It seems this is needed on every broker, not just observers? 21. Our

[jira] [Created] (KAFKA-10513) Newly added partitions are not assigned to running static consumer

Marlon Ou created KAFKA-10513: - Summary: Newly added partitions are not assigned to running static consumer Key: KAFKA-10513 URL: https://issues.apache.org/jira/browse/KAFKA-10513 Project: Kafka