[SERVER-53555] Performance regression for dropping/creating collections with requireApiVersion and majority write concern Created: 04/Jan/21  Updated: 29/Oct/23  Resolved: 23/Jan/21

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Bug Priority: Major - P3
Reporter: Divjot Arora (Inactive) Assignee: Xuerui Fa
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-56925 Remove requireApiVersion server param... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2021-01-25
Participants:

 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.



 Comments   
Comment by Githook User [ 23/Jan/21 ]

Author:

{'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}

Message: SERVER-53555: Ensure internal commands are not subject to requireApiVersion check
Branch: master
https://github.com/mongodb/mongo/commit/5d8bd0b1a0c861f9adb47a94faf635e47a45152a

Generated at Thu Feb 08 05:31:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.