[SERVER-32768] Ensure cluster has quiesced during sharded change streams passthrough after implicitly sharding collection Created: 18/Jan/18  Updated: 27/Oct/23  Resolved: 28/Jun/19

Status: Closed
Project: Core Server
Component/s: Sharding, Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Charlie Swanson Assignee: Backlog - Query Team (Inactive)
Resolution: Gone away Votes: 0
Labels: query-44-grooming
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Query
Operating System: ALL
Participants:
Linked BF Score: 26

 Description   

In order to resume a change stream, each shard in the cluster must know about the collection, until SERVER-32088 is resolved. If the implicit sharding of the collection that happens during sharded collections passthroughs such as change_stream_sharded_collections_passthrough fails to distribute the chunks amongst all shards, we may not be able to resume.



 Comments   
Comment by David Storch [ 28/Jun/19 ]

Since SERVER-32088 has been fixed, and the related build failure has been resolved, this ticket doesn't appear to be relevant anymore.

Generated at Thu Feb 08 04:31:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.