[SERVER-77207] Move sharding placement checks from opobservers to restore from yield Created: 16/May/23 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Gomez Ferro | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | PM-2144-QW-Fallout, oldshardingemea | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Participants: | |||||||||
| Description |
|
We are performing sharding placement checks (dbVersion and shardVersion) on op_observers, once per affected document. Once all write paths use collectionAcquisitions it is no longer necessary to check on the op_observers – collectionAcquisition's restore procedure already rechecks after a yield. |