[SERVER-5317] an empty database may be repeatedly, unnecessarily recloned Created: 14/Mar/12  Updated: 10/Dec/14  Resolved: 16/Jan/14

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

Type: Improvement Priority: Minor - P4
Reporter: Aaron Staple Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

        if ( ctx.justCreated() || empty || incompleteClone ) {
            // we must add to incomplete list now that setClient has been called
            incompleteCloneDbs.insert( clientName );
            if ( nClonedThisPass ) {

An empty database can potentially be recloned unnecessarily, as we always reclone if we see an empty db. This can be seen when the profile1.js test is run in small oplog mode. This test repeatedly drops profile1.system.profile, causing the slave to attempt to apply an op for the empty db 'profile1' (the op is a command so registered in namespace profile1.$cmd).

<http://buildbot.mongodb.org/builders/Linux%2064-bit%20DUR%20OFF/builds/879/steps/test_2/logs/stdio>


Generated at Thu Feb 08 03:08:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.