[SERVER-36632] Allow transaction operations against the config and admin databases excluding special collections Created: 14/Aug/18  Updated: 06/Dec/22  Resolved: 05/Mar/19

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

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

Issue Links:
Related
related to SERVER-43526 Re-enable commented test case in rest... Closed
Assigned Teams:
Sharding
Participants:

 Description   

Currently, all normal operations against the config or admin databases are disallowed in a transaction (excluding commit/abort/etc. against the admin db). This was done to prevent operations in transactions from touching special collections in those databases like config.transactions.

If instead we only disallow operations against the special collections, we could allow users to run operations against those databases in a transaction, which may be useful in a sharded cluster.



 Comments   
Comment by Gregory McKeon (Inactive) [ 05/Mar/19 ]

We aren't going to fix this now.

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