-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Labels:
-
Fully Compatible
-
ALL
-
v4.0
-
Sharding 2018-06-04
-
25
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.
- is duplicated by
-
SERVER-32024 Race between setting profiling level on a secondary and apply drop/create of database
- Closed