-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Replication
-
ALL
-
-
(copied to CRM)
When an applyOps entry causes a record to be upserted into the config.transactions table, it's impossible to know whether the entry changed the count of the collection or not. If it's a new session it will change the count, but if it's an existing session it won't. We would need to actually inspect the table for the existence of the session to correct this.
- is related to
-
SERVER-34977 subtract capped deletes from fastcount during replication recovery
- Closed
-
SERVER-35435 Renaming during replication recovery incorrectly allows size adjustments
- Closed
- related to
-
SERVER-39762 Fix fastcount after rollback recovery of prepared transactions.
- Closed
-
SERVER-42549 Remove TODO listed in SERVER-35483
- Closed
-
SERVER-43461 Complete TODO listed in SERVER-35483
- Closed
-
SERVER-59057 Do not enforce fast count in validate command for config.transactions collection
- Closed