-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.6.5
-
Component/s: Aggregation Framework
-
None
-
ALL
-
Query 2018-07-30
UUIDs were introduced in v3.6, however after upgrading from 3.4 it's possible that the collection state in-memory cache contains an entry for the collection (meaning it's sharded) but does not contain a UUID. As such, this assertion will fail when a $changeStream compares the UUID from the oplog entry to the UUID in the collection state cache.
Edit:
Since change streams requires readConcern majority, the secondary will perform a shard version check but not necessarily refresh its cache. For change streams, mongos will not attach a shard version which means that the version check will always pass and no refresh is performed.
- duplicates
-
SERVER-36154 Shard's in-memory CSS is not refreshed after upgrading from 3.4 to 3.6, causing a UUID mismatch on $changeStream operations
- Closed
- is duplicated by
-
SERVER-35379 com.mongodb.MongoQueryException: Query failed with error code 207 and error message 'Collection db.collection UUID differs from UUID on change stream operations' on server <host>
- Closed