Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-23110

dbeval with 'nolock' option checks for sharding metadata without collection lock

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.3.4
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 11 (03/11/16), Sharding 12 (04/01/16)
    • 0

    Description

      dbeval cannot be run on sharded collections and there are checks to prevent that. However when it is run with the 'nolock' option it will perform this check without holding collection lock, which causes invariant failure on debug builds.

      Attachments

        Activity

          People

            kaloian.manassiev@mongodb.com Kaloian Manassiev
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: