[SERVER-82673] Create commands that reserialize config.transactions as a clustered/nonclustered collection Created: 01/Nov/23  Updated: 09/Nov/23

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: James Bronsted Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-80862 Make config.transactions a clustered ... Closed
Assigned Teams:
Service Arch
Sprint: Service Arch Prioritized List
Participants:

 Description   

Following up on SERVER-80862, which asks to have the config.transactions table be created as a clustered collection, we need to address the upgrade concern of existing clusters gaining the performance benefit of clustered config.transactions as well as the downgrade concern of clusters expecting nonclustered config.transactions, but receiving clustered config.transactions.

 

Service Arch has proposed that commands be introduced that convert the config.transactions collection between the nonclustered and clustered formats, and that those commands be integrated into Atlas' upgrade/downgrade procedures (originally proposed in SERVER-80862 by max.hirschhorn@mongodb.com).


Generated at Thu Feb 08 06:49:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.