[SERVER-73988] Disable the dbVersion check on CheckShardFilteringMetadata test hook Created: 14/Feb/23 Updated: 29/Oct/23 Resolved: 15/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0, 6.3.0-rc2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| 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.3
|
||||||||||||||||||||
| Sprint: | Sharding EMEA 2023-02-20 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 20 | ||||||||||||||||||||
| Description |
|
The dbVersion metadata checks cannot be performed because shards (even db-primary shards) are allowed to have a stale notion of the dbVersion – they are not authoritative for it. For example, when createDatabase finishes, there's no guarantee that the new primary shard will have been made aware of it. The configsvr will do a best effort attempt at telling the primary shard to refresh, but in case of failover this may never be done. |
| Comments |
| Comment by Githook User [ 17/Mar/23 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: (cherry picked from commit 1c5a450ca3ba76d023d70ad0fea038f5c45236fd) |
| Comment by Liubov Molchanova [ 23/Feb/23 ] |
|
Requesting a backport for v6.3 as the issue reproduced in BFG-1819589, BFG-1821833 and some others. |
| Comment by Githook User [ 14/Feb/23 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |