Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
Query
-
ALL
-
Description
When a database is dropped and recreated, then profiling is turned on on a secondary, but the secondary replicates the drop/create after profiling is turned on, then the result is that profiling is off. From the client's perspective, the drop/create happened before turning on profiling on the secondary, so they would expect profiling to be on on the secondary.
Attachments
Issue Links
- duplicates
-
SERVER-32025 Ensure database drop/recreate is replicated before enabling profiling in safe_secondary_reads_drop_recreate.js
-
- Closed
-