[SERVER-79299] Drain 'shardCollections' as part of the setFCV process. Created: 25/Jul/23 Updated: 30/Oct/23 Resolved: 26/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pau Baldillou Salse (Inactive) | Assignee: | Pau Baldillou Salse (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding EMEA 2023-08-07 | ||||||||
| Participants: | |||||||||
| Description |
|
Let’s say that we deliver the new shardCollection in 7.1. Thus, when we are upgrading from 7.0 to 7.1, as part of the setFCV process we have to drain ‘shardCollections’ using the old implementation and start using the new one. Symmetrically, on FCV downgrade from 7.1 to 7.0 we have to drain shardCollections using the new implementation. |
| Comments |
| Comment by Githook User [ 26/Jul/23 ] |
|
Author: {'name': 'Pau Baldillou Salse', 'email': 'pau.baldillou-salse@mongodb.com', 'username': ''}Message: |