Hello,
I was wondering if anybody has seen the following:
I have a topic with about 200 partitions and with a replication factor of
3. Once in a while I am seeing a partition or two lose a replica. That is
the replica list for those partitions goes from 3 to 2 brokers. Kafka does
not see
Yeah, work around we’ve come up with is to use the Processor.init() method. We
confirmed that this is only called once all state stores for used by that
processor have been fully restored. From there, we iterate over the entire
store and (re)build our tracking map.
It seems to work well and is
Thanks.
I agree. Seems your options are limited. The API is not really a good
fix for what you want to do... Sorry.
-Matthias
On 1/18/23 7:48 AM, Upesh Desai wrote:
Hi Matthias, thanks for your reply! Sure, so the use case is as follows.
We currently store some time series data in the
Hi All,I've posted this question on SO about JVM heap usage wildly fluctuating
for a Broker which has no leader partitions.If anyone has a clue, please assist.
Kafka Broker JVM heap usage fluctuates wildly
|
|
|
| | |
|
|
|
| |
Kafka Broker JVM heap usage fluctuates wildly
I have 8
The Apache Kafka community is pleased to announce the release for Apache
Kafka 3.3.2
Apache Kafka 3.3.2 is a bugfix release and it contains, among other things,
fixes for 20 issues reported since 3.3.1.
All of the changes in this release can be found in the release notes:
Hi Titouan,
I've added you to our Jira project; you should be good to go now.
Cheers,
Chris
On Mon, Jan 23, 2023 at 10:41 AM Titouan Chary
wrote:
> Hi,
>
> It seems that JIRA access are disabled by default. Is it the right email to
> reach out in order to get a new JIRA account. I would like
Hi,
It seems that JIRA access are disabled by default. Is it the right email to
reach out in order to get a new JIRA account. I would like to participate
and give additional data points to the following ticket:
https://issues.apache.org/jira/browse/KAFKA-13077
Thanks in advance,
Regards,
Titouan
Ok, thanks Divij, I will check it.
---
Thanks & Regards,
Kunal Jadhav
On Mon, Jan 16, 2023 at 7:47 PM Divij Vaidya
wrote:
> Hey Kunal
>
> The stack trace you provided for the broker is from a non-controller node.
> The actual error occurs at the controller while processing the
>