I’m using Axon 3.3.5 with spring-boot and I’m trying to replay events in order to get databases sync. What I did was deleting my query db to get all the events from command db again.
there seems to be an issue with the KafkaTrackingToken in combination with how Kafka wants to coordinate consumers. This is being addressed at the moment.
the issue isn’t fixed yet in the master branch. It has been contributed by an external developer, so we’re also dependent on his availability. I’ll ping him for the progress.
in the Axon 4.0 release, we’ve moved the Kafka connector (as well as some other connectors) to different repositories. For Kafka, this is: https://github.com/AxonFramework/extension-kafka. There is currently one open issue, which covers the replay issue as well.
The KafkaConnector has not yet been released as 4.0, as we want this issue to be resolved first.
So I am assuming this issue is fixed in version 4 as I am not seeing it in the issue list anymore. I do have a question about this KafkaTrackingToken, is it just any offset of Kafka partition , or in case of multiple partitions on the topic, how is it achieving the tracking since Kafka does not guarantee ordering among different partitions.