[DOCS-12551] Clarify concurrency FAQ: How does concurrency affect a replica set primary? Created: 18/Mar/19  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Stennie Steneker (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: docs-onboarding-candidate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Description

On https://docs.mongodb.com/manual/faq/concurrency/#how-does-concurrency-affect-a-replica-set-primary, this FAQ response appears to be MMAP-specific:

How does concurrency affect a replica set primary?

With replica sets, when MongoDB writes to a collection on the primary, MongoDB also writes to the primary's oplog, which is a special collection in the local database. Therefore, MongoDB must lock both the collection's database and the local database. The mongod must lock both databases at the same time to keep the database consistent and ensure that write operations, even with replication, are "all-or-nothing" operations.

Scope of changes

  • Discuss w/ replication + storage team what the WiredTiger behavior is (for 4.2)
  • Discuss w/ replication + storage team what the MMAPv1 behavior is (for 4.0, 3.6)
  • Update documentation as required.

 



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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