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

convertToCapped is missing the 'global write lock' warning

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: manual
    • Labels:
      None
    • Last comment by Customer:
      true
    • Story Points:
      0.25

      Description

      http://docs.mongodb.org/manual/reference/command/convertToCapped/ does not mention that the command acquires a global write lock on the server, with all the dire consequences this can have on a live instance.
      The guide about "Converting a collection to capped" does mention it.

      It appears the mention was removed in DOCS-4502 allegedly because "This is no longer true in 2.8 due to SERVER-15826" back in 2014.
      I assume there was some confusion, as I found no evidence of the lock being actually removed, though it does switch to a DB lock in some cases after SERVER-15723 - a very recent change (3.4.10/3.5.10).

      If that report is confirmed, might a revert of mongodb/docs 72f694e be enough?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kevin.albertson Kevin Albertson
              Reporter:
              asiebert Adrien Siebert
              Participants:
              Last commenter:
              Kay Kim Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                4 years, 10 weeks, 4 days ago
                Date of 1st Reply: