[SERVER-66541] Clear the Collection Sharding State map during the setFCV command Created: 18/May/22 Updated: 29/Oct/23 Resolved: 20/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc11 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Sergi Mateo Bellido |
| 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: |
v6.0
|
||||
| Sprint: | Sharding EMEA 2022-05-30, Sharding EMEA 2022-06-13, Sharding EMEA 2022-06-27 | ||||
| Participants: | |||||
| Description |
|
The goal of this task is to clear the Collection Sharding State map (i.e. all collections) during the setFCV upgrade to 6.0. The reason to do that is to define a barrier from which all shards must know what they own at all moment. We can do this because since 5.3 we introduced a new migration protocol that guarantees that both donor and recipient update their filtering information as part of the commit phase. Before that, we had a weaker guarantee: the donor for sure knew about the migration but for the recipient we just triggered a best-effort refresh. This change should land on 6.0. |
| Comments |
| Comment by Githook User [ 20/Jun/22 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: |
| Comment by Githook User [ 20/Jun/22 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: Revert " This reverts commit 7bc0a21e572227371d79553a3263a142752fae56. |
| Comment by Githook User [ 14/Jun/22 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: Relying on config.cache.collections to signal secondary nodes |