[SERVER-32025] Ensure database drop/recreate is replicated before enabling profiling in safe_secondary_reads_drop_recreate.js Created: 17/Nov/17  Updated: 30/Oct/23  Resolved: 22/May/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.0.0-rc1, 4.1.1

Type: Bug Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-32024 Race between setting profiling level ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Sharding 2018-06-04
Participants:
Linked BF Score: 25

 Description   

In safe_secondary_reads_drop_recreate.js, we should ensure that the drop from the previous scenario is replicated before we enable profiling for the database on the secondaries. Otherwise, when the drop is replicated, the profile collection will be dropped. We can ensure the drop is replicated by giving the secondary votes, or by calling awaitReplication() before turning on profiling.



 Comments   
Comment by Githook User [ 22/May/18 ]

Author:

{'name': 'Matthew Saltz', 'email': 'matthew.saltz@mongodb.com'}

Message: SERVER-32025 Wait for replication in test before enabling profiling on secondary

(cherry picked from commit 3cd79c68c24b4899942f3f8084077fb8f8d0b4d3)
Branch: v4.0
https://github.com/mongodb/mongo/commit/827c31b20017aaee4c72fe284aacb0b798a692af

Comment by Githook User [ 22/May/18 ]

Author:

{'name': 'Matthew Saltz', 'email': 'matthew.saltz@mongodb.com'}

Message: SERVER-32025 Wait for replication in test before enabling profiling on secondary
Branch: master
https://github.com/mongodb/mongo/commit/3cd79c68c24b4899942f3f8084077fb8f8d0b4d3

Comment by Tess Avitabile (Inactive) [ 01/Dec/17 ]

Repurposing this ticket to describe the test fix to safe_secondary_reads_drop_recreate.js, since the Query team decided the race between replicating a drop/recreate and enabling profiling on a secondary is not a bug.

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