MM2 Source/Checkpoint connector update (#319)

Co-authored-by: Joyce Fee <[email protected]>
redpanda-data · Mar 5, 2024 · 4b102e8 · 4b102e8
1 parent daa4ced
commit 4b102e8
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 0 deletions.
diff --git a/...loyment-option/cloud/managed-connectors/create-mmaker-checkpoint-connector.adoc b/...loyment-option/cloud/managed-connectors/create-mmaker-checkpoint-connector.adoc
@@ -12,6 +12,11 @@ from other Kafka clusters.
 * A service account with read-only access to the external cluster is available.
 * The Kafka cluster topics connector is running for the same source cluster, with a matching configuration.
 
+== Limitations
+
+The MirrorMaker2 Checkpoint connector does not migrate consumer group offsets that are lower than the highest
+offsets synced by the MirrorMaker2 Source connector by the time the MirrorMaker2 Checkpoint connector is started.
+
 == Create a MirrorMaker2 Checkpoint connector
 
 To create the MirrorMaker2 Checkpoint connector:

diff --git a/.../deployment-option/cloud/managed-connectors/create-mmaker-source-connector.adoc b/.../deployment-option/cloud/managed-connectors/create-mmaker-source-connector.adoc
@@ -163,6 +163,10 @@ on the *Create Connector* page:
 | `Auto offset reset`
 | `consumer.auto.offset.reset`
 | What to do when there is no initial offset in Kafka, or if the current offset does not exist any more on the server (for example, because that data has been deleted). 'earliest' - automatically reset the offset to the earliest offset. 'latest' - automatically reset the offset to the latest offset. 'none' - throw exception to the consumer if no previous offset is found for the consumer's group.
+
+| `Offset lag max`
+| `offset.lag.max`
+| How out-of-sync a remote partition can be before it is resynced. This setting impacts the MirrorMaker2 Checkpoint connector as it is the maximum lag for syncing consumer groups. The default is 100 records.
 |===
 
 == Map data