[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: |
|
||||
| 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 |
| Comments |
| Comment by David Storch [ 28/Jun/19 ] |
|
Since |