[SERVER-22103] Getting timeout errors in Mongodb- While writing on primary to a single collection, does it provide write lock to the whole database Created: 08/Jan/16  Updated: 15/Nov/21  Resolved: 08/Jan/16

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

Type: Question Priority: Major - P3
Reporter: Aayushi Mangal Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:

 Description   

Would anybody please specify, I am writing to a collection in primary node, having following questions:

1) Does it provide write lock to database level while writing to the primary collection?

2) If write lock is there does it prevent any read operation?

3) PLeas eexplain how concurrency work in Replica set, while inserting is performing on primary's single collection .

4) Does one collection is affects persofmance of othe collection residing under same database ?



 Comments   
Comment by Ramon Fernandez Marina [ 08/Jan/16 ]

Thanks for your report aayushi. Depending on the storage engine, MongoDB 3.0 provides either collection-level or document-level locking.

Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. See also our Technical Support page for additional support resources.

A question like this involving more discussion would be best posted on the mongodb-user group. If you're seeing timeouts you'll need to provide more details about your application, setup, and possibly server logs.

Regards,
Ramón.

Generated at Thu Feb 08 03:59:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.