[SERVER-72496] Investigate config.transactions collection and index validation Created: 03/Jan/23 Updated: 29/Oct/23 Resolved: 17/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Colin Stolley | Assignee: | Mohammad Dashti (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm2646-m4 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
When implementing validation for CSI, we found two collections which apparently do not update indexes when written to, namely:
geert.bosch@mongodb.com commented in a discussion with charlie.swanson@mongodb.com that such behavior is not unexpected in local.replset.oplogTruncateAfterPoint , but we don't know for sure about config.transaction. We'd like to get someone to confirm this. We have a failpoint which puts CSI on all collections for testing, but these two collections are exempt (via this helper function). We want to be sure that is the correct thing to do. |
| Comments |
| Comment by Githook User [ 17/Jan/23 ] |
|
Author: {'name': 'Mohammad Dashti', 'email': 'mdashti@gmail.com', 'username': 'mdashti'}Message: |
| Comment by Geert Bosch [ 13/Jan/23 ] |
|
Yes, don't try and create CSI indexes on these internal collections, it really doesn't make sense. |