[SERVER-42723] New shard with new database can be ignored by change streams Created: 08/Aug/19  Updated: 29/Oct/23  Resolved: 17/Oct/19

Status: Closed
Project: Core Server
Component/s: Aggregation Framework, Querying, Sharding
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Bug Priority: Major - P3
Reporter: Charlie Swanson Assignee: Bernard Gorman
Resolution: Fixed Votes: 0
Labels: query-44-grooming
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
Related
related to SERVER-44039 Improve $changeStream handling of clu... Backlog
related to SERVER-44356 Change Stream latency is determined b... Closed
is related to SERVER-44112 The ChangeStream test fails on the la... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Query 2019-08-26, Query 2019-09-09, Query 2019-09-23, Query 2019-10-07, Query 2019-10-21, Query 2019-11-04
Participants:
Linked BF Score: 49

 Description   

We think it is possible to add a shard, create a new database on that shard, and then create one or more unsharded collections on that shard without a change stream noticing that the shard exists.

The execution machinery uses an oplog entry indicating a migration to detect that a new shard has been added. But in the scenario above there may be no information in any of the shards' oplogs to indicate that a new shard exists.



 Comments   
Comment by Githook User [ 22/Dec/19 ]

Author:

{'name': 'Bernard Gorman', 'email': 'bernard.gorman@mongodb.com', 'username': 'gormanb'}

Message: SERVER-42723 Set 'use44SortKeys' on change stream sent to config servers
Branch: master
https://github.com/mongodb/mongo/commit/8034abccfe1e26e0957fd52906f8e52840b3ae43

Comment by Githook User [ 17/Oct/19 ]

Author:

{'username': 'gormanb', 'email': 'bernard.gorman@mongodb.com', 'name': 'Bernard Gorman'}

Message: SERVER-42723 New shard with new database can be ignored by change streams
Branch: master
https://github.com/mongodb/mongo/commit/97cc7b5838db4ef13ede3149c44bceca8f5c2977

Generated at Thu Feb 08 05:01:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.