Mongo Connector: Inconsistent snapshot data for sharded cluster [DBZ-8658]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-8658](https://issues.redhat.com/browse/DBZ-8658)
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
h1. Bug report
For bug reports, provide this information, please:
h2. What Debezium connector do you use and what version?
MongoDB Connector
h3. Description
Debezium Connector doesn't use readConcern parameter currently. In case of sharded cluster, snapshot data will be inconsistent as it will be determined by readConcern set by database/collection. Connector should use "snapshot" read concern as stated in mongodb docs - [https://www.mongodb.com/docs/manual/reference/read-concern-snapshot/,] so that consistent snapshot data is read.
https://debezium.zulipchat.com/#narrow/channel/348106-community-mongodb/topic/Consistent.20snapshot.20data.20for.20a.20sharded.20mongo.20cluster
Contributor guide
Assessment
This issue has not been assessed yet.