7 534
> Grand Parade part of William Hill
> ul. Kotlarska 11 | 31-539 Krakow
> From: Sejal Patel
> Date: Monday, 17 June 2024 at 14:16
> To: users@kafka.apache.org ,
> kafka-clie...@googlegroups.com ,
> d...@kafka.apache.org , Wojciech Frycz
>
> Cc: Cezary Gajdzinski
he bug is fixed but not
> going to be released until 3.7.1 comes out. The bug prevented metadata from
> being readable and thus anytime a node restarted (including the kraft server
> itself), it could never come back online or be unregistered from the cluster
> either.
> Sejal [Patel]
Hey folks,
I'm quite confused here. I have a random partition that has 4 replications
instead of 3. I don't have a clue how to fix it or what the ramifications of
this are either. There are no repartitioning happening or reassignments or
anything at all. This looks like the metadata is just wron
metadata from
being readable and thus anytime a node restarted (including the kraft server
itself), it could never come back online or be unregistered from the cluster
either.
Sejal [Patel] | CTO
se...@playerzero.ai <mailto:se...@playerzero.ai> | 470.440.1255
On Thu Jun 13, 2024, 03:26
second if
it issue seeing a reason to shift work around. But I'm more confident that
you'll not be spinning up more consumers than you have total partitions to
start with cause there are a lot of partitions happening with the Kafka stores
each having some as well.
Sejal [Patel] | CTO
a
> There is also an open Kafka Jira Ticket
> https://issues.apache.org/jira/browse/KAFKA-16662
> We fixed it by downgrading to 3.6.
>
> Hope this helps.
>
> -Ursprüngliche Nachricht-
> Von: Sejal Patel
> Gesendet: Montag, 3. Juni 2024 08:26
&
I was expanding my kafka cluster to 24 nodes (from 16 nodes) and rebalancing
the topics. 1 of the partitions of the topic did not get rebalanced as expected
(it was taking a million years so I decided to look and see what was
happening). It turns out that the script for mounting the 2nd partitio
Hi, I was expanding my kafka cluster to 24 nodes (from 16 nodes) and
rebalancing the topics. 1 of the partitions of the topic did not get rebalanced
as expected (it was taking a million years so I decided to look and see what
was happening). It turns out that the script for mounting the 2nd part
