Hello Akash,
I will try by changing compression type and test if the issue persists, but
for now the issue is resolved I guess. I just changed replication_factor of
the topic to 3. It was like a 3-node kafka cluster and replication_factor
was configured 2 for the topic.
On Wed, Aug 28, 2024 at 2:
Sounds like https://issues.apache.org/jira/browse/KAFKA-16394
-Matthias
On 8/29/24 02:35, Vogel, Kevin, DP EPS, BN, extern, external wrote:
Hello there,
I searched the Apache Jira for a bug report on this topic but couldn't find
one. Maybe anyone else has noticed something similar or knows mo
Hi Tim,
Thanks for your interest in Apache Kafka.
The page you mention is still contains valid information regarding the End
of Life cycle: Apache Kafka maintains the latest 3 versions. Currently,
this means 3.6.2, 3.7.1 and 3.8.0.
In a few weeks we hope to have released 3.9.0, which would then i
hi all.
can someone point me to a reference that describes the apache kafka release
lifecycle and/or a page that has EoL dates for various versions?
i'm looking for information on what versions of the product are currently
supported by the community, and dates/information that outlines when tha
Hello
Kafka brokers are designed to be dumb i.e. they simply act as a pipe to
transmit messages from producer to consumer. They don’t have capabilities
to selectively filter or perform any analytics/transformation of the
messages in flights. In fact, a brokers doesn’t ever read the key/value
pair
Hi Kafka users,
I have a producer consumer setup where I want the consumer to get only a subset
of messages based on some conditions.
Trying to figure out whether there are any configuration on the Kafka side that
we can do to achieve this . Most of the solutions I see is to filter them at
th
Thanks, Luke. Both the static and dynamic options for configuring unclean
leader election now work in 3.9, thanks to your help.
Dima, if you have only a transient need to do an unclean leader election, using
the kafka-leader-election.sh script is still the best way. It avoids the risk
for forge
Hello there,
I searched the Apache Jira for a bug report on this topic but couldn't find
one. Maybe anyone else has noticed something similar or knows more about this.
After we updated our Spring Boot Kafka Streams application kafka-streams
dependency from 3.6.2 to 3.7.1, we noticed some failin
Hi All, Trying to avoid the rebalance operation on the kafka connect client (2
node/distributed mode) with Kafka 2.5.1
The connect client side properties were updated from default to higher
value.session.timeout.ms=30
heartbeat.interval.ms=10
While this helps in avoid rebalances, a node
[re-send]
Hi All, Trying to avoid the rebalance operation on the kafka connect client
(2 node/distributed mode) with Kafka 2.5.1
The connect client side properties were updated from default to higher
value.session.timeout.ms=30
heartbeat.interval.ms=10
While this helps in avoid rebalan
10 matches
Mail list logo
