Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-7300

concurrency docs page needs improvement

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • 01112017-cleanup
    • None
    • None
    • None

    Description

      https://docs.mongodb.org/manual/faq/concurrency/

      This page I think has became quite confusing over many iterations as releases have gone by. A lot of the content is about mmap but mmap is not hte default storage engine anymore.

      Further the WiredTiger section itself says:

      For most read and write operations, WiredTiger uses optimistic concurrency control. WiredTiger uses only intent locks at the global, database and collection levels. When the storage engine detects conflicts between two operations, one will incur a write conflict causing MongoDB to transparently retry that operation.
      Some global operations, typically short lived operations involving multiple databases, still require a global “instance-wide” lock. Some other operations, such as dropping a collection, still require an exclusive database lock.

      It would be easy for the reader to infer from reading this that there is no document level concurrency with WildTiger.

      Some mention of pluggable storage engines right at the top might be helpful.

      Attachments

        Activity

          People

            Unassigned Unassigned
            dwight@mongodb.com Dwight Merriman
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              7 years, 50 weeks, 2 days ago