[SERVER-70161] Optimize the compound index of config.placementHistory Created: 03/Oct/22 Updated: 29/Oct/23 Resolved: 04/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | Paolo Polato |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-10-17 |
| Participants: |
| Description |
|
The config.placementHistory collection is currently supported by a compound index defined as {nss: 1, timestamp: 1}; nevertheless, most queries sort documents in descending order of timestamp. |
| Comments |
| Comment by Githook User [ 04/Oct/22 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: |