[SERVER-61026] Invert order of shards receiving drop collection participant command Created: 27/Oct/21 Updated: 29/Oct/23 Resolved: 27/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 5.0.3, 5.1.0-rc2 |
| Fix Version/s: | 5.2.0, 5.0.4, 5.1.0-rc3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v5.1, v5.0
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Both drop database and drop collection coordinators are sending the drop participant command first to the primary shard and then to the others. As a result, the current behavior permits to see the following change stream events (thanks max.hirschhorn for pointing that out):
It would be difficult for a client to know whether the insert (2) happened during or after the drop. Inverting the order would prevent such interleaving of events. |
| Comments |
| Comment by Githook User [ 28/Oct/21 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 28/Oct/21 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 27/Oct/21 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |