[SERVER-28989] Avoid dropping dummy database in ReplSetTest.prototype.checkReplicaSet() Created: 26/Apr/17  Updated: 30/Oct/23  Resolved: 28/Apr/17

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.4.15, 3.5.7

Type: Improvement Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: bkp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-25196 collMod should support writeConcern Closed
depends on SERVER-28507 Make all command implementations igno... Closed
Duplicate
is duplicated by SERVER-33498 ReplSetTest.checkReplicaSet fails whe... Closed
Related
related to SERVER-30900 remove collMod writeConcern argument ... Closed
is related to SERVER-26624 Create test command that will block u... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4
Sprint: TIG 2017-05-08
Participants:
Linked BF Score: 0

 Description   

The ReplSetTest.prototype.checkReplicaSet() function drops the dummy database to avoid leaving around any unnecessary data files; however, repeatedly creating and dropping a database with a unique name incurs a significant amount of I/O overhead when running with the MMAPv1 storage engine since data files must be allocated and deleted each time, respectively. Given that the procedure for flushing any pending background index builds is performed by running a "collMod" command for each collection, there's no requirement that the database for the w=all replicated write needs to have a unique name.

// Since we cannot determine if there is a background index in progress (SERVER-26624),
// we flush indexing as follows:
//  1. Iterate through all collections and run collMod against each (collMod will block
//     replication to wait for any active background index builds to complete)
//  2. Insert a document into a dummy collection with a writeConcern for all nodes (which
//     will block on completion of the background index build + collMod)



 Comments   
Comment by Githook User [ 25/Mar/18 ]

Author:

{'email': 'max.hirschhorn@mongodb.com', 'name': 'Max Hirschhorn', 'username': 'visemet'}

Message: SERVER-28989 Avoid dropping dummy database in checkReplicaSet().

(cherry picked from commit 5c702fedb3216b1a327d3791cd9e995fefc4ab2f)

SERVER-30900 removed unnecessary writeConcern from collMod command in
ReplSetTest.checkReplicaSet()

(cherry picked from commit ac84a0d028eff2b8ca42817d998cb8b34563816c)
Branch: v3.4
https://github.com/mongodb/mongo/commit/b910f64caeac3761445eed604fceaf0698e02447

Comment by Githook User [ 28/Apr/17 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-28989 Avoid dropping dummy database in checkReplicaSet().
Branch: master
https://github.com/mongodb/mongo/commit/5c702fedb3216b1a327d3791cd9e995fefc4ab2f

Generated at Thu Feb 08 04:19:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.