[SERVER-85136] Audit/rework Concurrency FAQ Created: 16/Feb/15  Updated: 12/Jan/24  Resolved: 23/Mar/15

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

Type: Task Priority: Major - P3
Reporter: Michael Paik Assignee: Geert Bosch
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Docs Sprint 17 - Ending 4/3, Quint Iteration 3.1.1
Participants:

 Description   

kaloian.manassiev, can you take a look through http://docs.mongodb.org/manual/faq/concurrency/ and audit it for correctness? Dan said that you were probably the right person for this.



 Comments   
Comment by Githook User [ 23/Mar/15 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: WRITING-1212: Initial version of concurrency FAQ update

Signed-off-by: kay <kay.kim@10gen.com>
Branch: master
https://github.com/mongodb/docs/commit/efbbe48f3c76999f20d561d936ec08502f299da1

Comment by Kaloian Manassiev [ 19/Feb/15 ]

Passing it back to you michael.paik. Let me know if there is anything else you need from me.

Comment by Kaloian Manassiev [ 17/Feb/15 ]

I actually don't understand what is the intended audience of this FAQ. Is it supposed to be a lecture on MongoDB concurrency or a point of reference to other documentation that we have on locks?

Here is some points I would make:

  • It should be changed to no longer refer to database level locking, but collection (MMAPV1) or document (WT).
  • Should explain the purpose of the journal lock and what stalls on this lock mean (MMAP V1).
  • Explain optimistic concurrency control in WT and what does 'write conflict exception' means.
  • Should explain intent modes and why are they needed.
Comment by Michael Paik [ 17/Feb/15 ]

As part of the initial audit, you'll want to point out what is missing or wrong where so we can characterize the work.

Comment by Kaloian Manassiev [ 17/Feb/15 ]

I can source you with the material, but I don't want to write the new page

I put it all here: https://drive.google.com/open?id=0B5raYvDzh00-fjY2bkVDUHd5aVJFWVhCa25kV0J2bXB5QmZ6ZE8wbllDY3FBWjgxZjU1bFE&authuser=0

Let me know if you have any questions.

Comment by Michael Paik [ 17/Feb/15 ]

It looks like we failed to capture the need for documentation changes related to the associated server tickets and will need to rewrite this page - there is no updated documentation as yet. If you are not the correct person to source this material, can you point us to the appropriate party?

Comment by Kaloian Manassiev [ 17/Feb/15 ]

I opened this link and clicked on 3.0 (upcoming) from the drop down menu and the content is completely out of date for 3.0 - it misses collection locking, lock hierarchies, etc. When is the updated documentation coming for me to audit?

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