Details
-
Enhancement
-
Resolution: Done
-
Major
-
2.2.0.Alpha2
-
None
-
False
-
None
-
False
Description
Currently for sharded clusters Debezium opens a connection to each shard's replica set directly for snapshot and streaming.
While this approach should allow for a higher throughput due to utilised parallelism,[ it is not recommended by MongoDb|https://www.mongodb.com/docs/manual/sharding/#connecting-to-a-sharded-cluster]
We should provide a way to utilise proper connection via mongos instance. However this solution should be backwards compatible – at least for the lifespan on 2.x release line.
Additionally this will allow support of incremental snapshotting for sharded deployments as well as total ordering of captured change events.
Attachments
Issue Links
- depends on
-
DBZ-6032 Refactor connection management for mongodb connector
-
- Closed
-
-
DBZ-5987 Refactor snapshotting to use change streams instead of oplog
-
- Closed
-
- incorporates
-
DBZ-4427 Complete MongoDB incremental snapshotting implementation
-
- Closed
-
-
DBZ-5590 Capture evenents in order across mongodb shards
-
- Closed
-
- links to
-
RHEA-2023:120698 Red Hat build of Debezium 2.3.4 release