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

Performance regression for dropping/creating collections with requireApiVersion and majority write concern

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.9.0
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2021-01-25

    Description

      Testing against server version 4.9.0-alpha-1124-ge369908, I locally see dropping a non-existent collection and then explicitly creating it take ~10 seconds if each node in the replica set has the requireApiVersion parameter set to "1" and both the "drop" and "create" commands are run with majority write concern. If the parameter is not set, both commands execute in under one second.

      I've reproduced results using this Python script: https://gist.github.com/divjotarora/29c523b726933192d563b823a2f8abbd. Running "python3 main.py" will execute both a "drop" and "create" command. Additionally, "python3 main.py --setParamter" will first set the requireApiVersion parameter to '1' on each node in the cluster.

      Attachments

        Issue Links

          Activity

            People

              xuerui.fa@mongodb.com Xuerui Fa
              divjot.arora@mongodb.com Divjot Arora
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: