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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.3.4
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 11 (03/11/16), Sharding 12 (04/01/16)
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Kaloian Manassiev
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: