[SERVER-62552] Cluster some internal system collections by default Created: 12/Jan/22  Updated: 04/Dec/23  Resolved: 07/Jun/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Louis Williams Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Related
related to SERVER-66252 Create a way to convert a nonclustere... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-05-16, Execution Team 2022-05-30, Execution Team 2022-06-13
Participants:
Linked BF Score: 0

 Description   

After 6.0 is released, consider having all new internal collections be clustered by _id. Do not attempt to upgrade existing, unclustered collections.

We must do this after 6.0 to simplify downgrading from 6.1/7.0 to 6.0.



 Comments   
Comment by Louis Williams [ 07/Jun/22 ]

This change clusters internal oplog buffer collections for initial sync, resharding, and tenant migrations. This should help reduce cache usage and speed up these operations. I explored clustering some other internal collections but didn't see any significant benefits.

Comment by Githook User [ 07/Jun/22 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-62552 Cluster internal oplog buffer collections
Branch: master
https://github.com/mongodb/mongo/commit/e77e6bd549a2564cbdba8498a8a9d8b28da955da

Generated at Thu Feb 08 05:55:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.