Heartbeat topic configuration for Kafka Source Connector

Hi.

We are considering using heartbeat mechanism to prevent the loss of the resume token when reading changes from a collection.

Our current scenario involves 6 collections being polled, each by one separate connector.

So far, we haven’t found any documentation about the heartbeat topic parameters. Any advise on how to choose, topic retention, topic partition number, compaction… or any other relevant heartbeat topic configs?

Also, given our scenario of several connectors, is it safe to share the heartbeat topic or should we create a separate topic per connector?

Thanks

2 Likes