In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

Mongodb 1.9

What is the connector configuration?

{
"name": "mds_atlas_amr_mongodb_connector_cdc_large1_1",
"config":

{ "connector.class": "io.debezium.connector.mongodb.MongoDbConnector", "errors.log.include.messages": "true", "max.queue.size": "8192", "topic.creation.default.partitions": "1", "topic.creation.default.max.message.bytes": "20971520", "mongodb.password": "***", "tasks.max": "3", "capture.mode": "change_streams_update_full", "snapshot.delay.ms": "100", "confluent.topic.ssl.endpoint.identification.algorithm": "https", "collection.whitelist": "machinedata.cellular_activity_events,machinedata.therapy_measurements,machinedata.system_activity_events", "provide.transaction.metadata": "true", "tombstones.on.delete": "false", "topic.prefix": "mds_atlas_amr_cdc_large_cdc", "cursor.max.await.time.ms": "500", "mongodb.authsource": "admin", "topic.creation.default.replication.factor": "3", "initial.sync.max.threadsinitial.sync.max.threads": "1", "value.converter": "org.apache.kafka.connect.json.JsonConverter", "database.whitelist": "machinedata", "errors.log.enable": "true", "mongodb.hosts": "config1/10.154.9.121:27017,config2/10.154.10.12:27017,config3/10.154.8.12:27017", "snapshot.fetch.size": "0", "key.converter": "org.apache.kafka.connect.json.JsonConverter", "topic.creation.default.compression.type": "snappy", "confluent.topic.bootstrap.servers": "***", "topic.creation.default.cleanup.policy": "delete", "connect.max.attempts": "16", "mongodb.document.converter.schemas.enable": "false", "mongodb.user": "kafka-user", "mongodb.name": "mds_atlas_amr_cdc_large_cdc", "max.request.size": "2097164", "key.converter.schemas.enable": "false", "producer.override.max.request.size": "20971520", "name": "mds_atlas_amr_mongodb_connector_cdc_large1_1", "value.converter.schemas.enable": "false", "max.batch.size": "2048", "snapshot.mode": "never" }

What is the captured database version and mode of depoyment?

currently on EC2's on aws and migrating it to atlas cloud

What behaviour do you expect?

Is there any document which we can refer for migrating to atlas cloud?

What behaviour do you see?

How can we ensure that we maintain the same oplog position in Atlas after migration?So that the connector starts reading from the same point where it left. Previously, encountering connector failures due to oplog size necessitated deploying a new connector. Can we avoid such failures with Atlas? Additionally, since we currently connect to config servers, but Atlas does not offer this option, what is the best approach moving forward?

Do you see the same behaviour using the latest relesead Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

<Your answer>

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

<Your answer>

How to reproduce the issue using our tutorial deployment?

<Your answer>

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

<Your answer>

Implementation ideas (optional)

<Your answer>