[SERVER-62874] Investigate unknown sharding_clustered_collections suite failures Created: 21/Jan/22 Updated: 29/Oct/23 Resolved: 03/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Daniel Gomez Ferro |
| 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: | Execution Team 2022-02-07 | ||||||||
| Participants: | |||||||||
| Description |
|
Check for tests listed under this TODO in sharding_clustered_collections.yml |
| Comments |
| Comment by Githook User [ 03/Feb/22 ] |
|
Author: {'name': 'Daniel Gómez Ferro', 'email': 'daniel.gomezferro@mongodb.com', 'username': 'dgomezferro'}Message: |
| Comment by Haley Connelly [ 25/Jan/22 ] |
|
If documents are being skipped, check and see if SimpleSort is being used internally, when the caller expects the RecordId, and the document gets skipped over. See |