[SERVER-34811] Forbid reads and writes to the config, admin, and local databases within transactions Created: 02/May/18  Updated: 29/Oct/23  Resolved: 08/May/18

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Tess Avitabile (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-11692 Docs for SERVER-34811: Forbid reads a... Closed
Related
is related to SERVER-34920 Reading the oplog in a txn is permitt... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-05-21
Participants:

 Comments   
Comment by Githook User [ 08/May/18 ]

Author:

{'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile', 'username': 'tessavitabile'}

Message: SERVER-34811 Forbid reads and writes to the config, admin, and local databases within transactions
Branch: master
https://github.com/mongodb/mongo/commit/98f28d452b9b330d6c1696d6d8207b582a5870fc

Comment by Spencer Brody (Inactive) [ 02/May/18 ]

I think SERVER-33115 is valuable to leave in-place.  It calls  ReplicationCoordinator::isOplogDisabledFor, which checks more than just the database name.

Comment by Tess Avitabile (Inactive) [ 02/May/18 ]

I think we are safe there, since the foreign collection must be in the same database.

Comment by James Wahlin [ 02/May/18 ]

This should include foreign collection reads via $lookup and $graphLookup.

Comment by Tess Avitabile (Inactive) [ 02/May/18 ]

If we ban all commands on local, we should probably undo the work in SERVER-33115, which bans writes.

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