[SERVER-29884] Rename session transactions collection to config.system.transactions Created: 28/Jun/17  Updated: 06/Dec/22  Resolved: 15/Sep/17

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-30690 Disallow retryable writes unless FCV ... Closed
Assigned Teams:
Sharding
Participants:

 Description   

Currently, the session transactions collection is persisted under config.transactions. It should be renamed to go under the config.system.transactions namespace and should only be created if the server is running in 3.6 compatibility mode so that older replica set members will not reject its creation.



 Comments   
Comment by Kaloian Manassiev [ 15/Sep/17 ]

The config database already requires special permission to be accessed so there is no pressing need to move the transactions collection under system.transactions.

Furthermore, the config database is intended for internal purposes only and should not be written to by users.

Because of these considerations, closing this ticket as Won't Fix.

Generated at Thu Feb 08 04:22:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.