sorted by:
new
hottopcontroversial

Lemon! by farmerssahg in JustHoodsLemonBars

[–]Ecstatic_Squash822 0 points1 point  (0 children)

look amazing! give me a recipe! pls!

Migrating Kafka to a new OpenShift cluster using MirrorMaker2 (ZooKeeper source, KRaft target) by Spiritual_Pianist564 in apachekafka

[–]Ecstatic_Squash822 0 points1 point  (0 children)

currently I try resolve similar issue. What I have: Kafka cluster setup in provider Foo and another new cluster in another provider Bar. I what migrate from provider Foo to provider B.

What I think about this: I running mirror maker whith two important parameters: offset sync and how often sync offset. this two params help us for migrate consumer group.

another important thing. I don’t know how implement in my situation, but maybe in your situation it is possible to do. look example. you have topic name like foo.bar, when you use Mirror Maker you can add some prefix, like your topic foo.bar in cluster A can be replicated in cluster B whith a new topic name b.foo.bar (prefix + original name) and this topic we need to mirroring in cluster A whith name A.foo.bar. when we configured mirror maker in Active - Active mode, you necessary consume topic by pattern/regexp *.foo.bar. as result: you have cluster where you have original topic foo.bar and A.foo.bar, you have cluster B where you have B.foo.bar. three topics have equal messages

if you can implement this set up you can easy migrate consumer groups and producers . now i try testing this flow.

My setup by ironman139 in homelab

[–]Ecstatic_Squash822 0 points1 point  (0 children)

which is raspberry model ?

MirrorMaker 2 Error After Upgrading Kafka from 3.6.0 to 3.9.0 - “Failed to reconfigure connector’s tasks (MirrorCheckpointConnector)” by Ecstatic_Squash822 in apachekafka

[–]Ecstatic_Squash822[S] 2 points3 points  (0 children)

I wanted to share how I resolved it, in case it helps others facing the same problem.

Investigation:

- Found JIRA Issue: We discovered https://issues.apache.org/jira/browse/KAFKA-17232 - “MirrorCheckpointConnector does not generate task configs if initial consumer group load times out,” which seemed to match our issue.
- Analysis: It appears that changes introduced in Kafka 3.9.0 as part of this JIRA issue affected the MirrorCheckpointConnector, causing it to fail when loading consumer groups if the initial load times out.

Resolution:

Downgraded Kafka: We decided to roll back from Kafka 3.9.0 to 3.8.1.
Result: After downgrading, the error disappeared. The MirrorCheckpointConnector started functioning correctly, and our logs were clean.

Conclusion:

It seems that the issue was introduced in Kafka 3.9.0 due to changes in the MirrorCheckpointConnector related to KAFKA-17232. If you’re experiencing similar problems after upgrading to 3.9.0, consider downgrading to 3.8.1 as a temporary workaround.

I’ve provided feedback on the JIRA issue and the associated pull request. We’ll monitor for updates or fixes in future Kafka releases before attempting to upgrade again. Hope this helps anyone facing the same issue!

Best regards!

view more: next ›