This is how the assignment looks like after full restart. N represents node
and the second column is the number of partitions assigned. There are just
two input topics with equal partitions in the topology. I was expecting
each node to have 6 partitions assigned.
N1 7
N2 5
N3 7
N4 5
N5 7
N6 5
N7 7
We are using kafka version 2.6.1 on broker and 2.6.2 for streams.
Thanks
On Wed, Jun 2, 2021 at 7:18 PM Navneeth Krishnan
wrote:
> Hi All,
>
> We recently migrated from flink to kafka streams in production and we are
> facing a major issue. Any quick help would really be appreciated.
>
> There
Hi All,
We recently migrated from flink to kafka streams in production and we are
facing a major issue. Any quick help would really be appreciated.
There are 72 input data topic partitions and 72 control stream topic
partitions. There is a minimum of 12 nodes with 6 streams threads on each
instan
Hi all,
Hoping someone can sanity check my logic!
A cluster I'm working on went into production with some topics poorly
configured; ReplicationFactor of 1 mostly being the issue.
To avoid downtime as much as possible, I used the
kafka-reassign-partitions.sh tool to add extra replicas to topic par
Hi,
What is the impact on performance while using kafka rest proxy.
Does it affect other kafka producers (or) clients in any which way?
What is the downside/disadvantages of using kafka rest proxy.
Please clarify.
Thanks,
Vinay