Broker Failure Recovery - Disk or Replication?

Hi, I wanted to understand more on how a broker recovers from a failure. As far as I understand, when a broker recovers from a failure, it 1) loads data of all partitions it hosted from the disk (the metadata about the partitions would exist in zookeeper, right?)2) then syncs with the leader of

[ANNOUNCE] Apache Kafka 3.4.1

The Apache Kafka community is pleased to announce the release for Apache Kafka 3.4.1. This is a bug fix release and it includes fixes and improvements from 58 JIRAs, including a few critical bugs: - core KAFKA-14644 Process should stop after failure in raft IO thread KAFKA-14946 KRaft controller n

Re: [VOTE] 3.5.0 RC1

+1 (non-binding) ... I used the staged binaries with Scala 2.13 and staged artifacts to run my tests. All seems to work fine. Thanks for running the release Mickael! Jakub On Mon, Jun 5, 2023 at 3:39 PM Mickael Maison wrote: > Hello Kafka users, developers and client-developers, > > This is th

Re: [VOTE] 3.5.0 RC1

Hi Mickael, I did the following checks: - Signature, checksum, licenses - Build from source with Java 17 and Scala 2.13 - Full unit and integration test suites - Java app with staging Maven artifacts and multi-node cluster LGTM, apart from the already mentioned "classgraph" license that can be re

Re: [EXTERNAL] [MirrorMaker2] Missing «kafka.connect.mirror:type=MirrorCheckpointConnector» Mbean

Hello, Is it that no one else encountered such case? =( From: Iermulnik, Georgii Sent: 01 June 2023 22:55 To: users@kafka.apache.org Subject: [EXTERNAL] [MirrorMaker2] Missing «kafka.connect.mirror:type=MirrorCheckpointConnector» Mbean CAUTION: External source

Re: kafka 3.4.0 sasl_PLAINTEXT kafka-metadata-quorum.sh Unexpected Kafka request of type METADATA during SASL handshake

Hi, I've replied you in your previous email. https://lists.apache.org/thread/ogzpxtnsyklp7q82xh5t0y58rgtpc18x Please take a look. Thanks. Luke On Tue, Jun 6, 2023 at 5:13 PM Yj Jia wrote: > > > kafka 3.4.0 sasl_PLAINTEXT exec kafka-metadata-q

kafka 3.4.0 sasl_PLAINTEXT kafka-metadata-quorum.sh Unexpected Kafka request of type METADATA during SASL handshake

kafka 3.4.0 sasl_PLAINTEXT exec kafka-metadata-quorum.sh Unexpected Kafka request of type METADATA during SASL handshake. 1、kafka 3.4.0 config broker sasl_PLAINTEXT, ./kafka-metadata-quorum.sh --bootstrap-server 192.168.3.138:9092 --command-con

Re: Kafka Stream: Cannot invoke "org.apache.kafka.streams.processor.internals.SourceNode.getTimestampExtractor()" because "source" is null

Hi Andrew, what version of Kafka Streams do you use? Since 2.7 there is a null check for the source node [1]. The following ticket might be related: https://issues.apache.org/jira/browse/KAFKA-10205 Best, Bruno [1] https://github.com/apache/kafka/blob/20028e24cca91422b8f02fdbf45d2cd9ef24c9

Re: [VOTE] 3.5.0 RC1

Hi Mickael, I ran the following validation steps: - Built from source with Java 17 and Scala 2.13 - Signatures and hashes of the artifacts generated - Navigated through Javadoc including links to JDK classes - Run the quickstart in KRaft and Zookeeper mode +1 (binding) from me. Thanks for running