Closed travnewmatic closed 3 years ago
You need to keep the polylith component DBs in sync with the Kafka database as they store offsets into the Kafka topics. This is the reason why they fail to start up.
Closing this as a configuration issue, and also because we are going to move away from Kafka in the future to use NATS.
Background information
go version
: whatever comes in the containerDescription
federation sender
andsync api
do not restart gracefully.Steps to reproduce
Error for both (i think):
kafka server: The requested offset is outside the range of offsets maintained by the server for the given topic/partition.
federation sender logs:
sync api logs:
i'm able to restart both containers (pods) by dropping and recreated their respective databases.