-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 3.1.3
-
Component/s: Replication
-
Fully Compatible
-
ALL
-
-
RPL 5 06/26/16
-
0
If profiling is enabled on a secondary and a system.profile drop occurs on the primary, the secondary will abort, as of 3.1.2.
In previous versions, including 3.0.4-rc0, the same set of operations would result in a warning and a failed drop.
3.1.2+
I COMMAND [repl writer worker 15] CMD: drop test.system.profile E REPL [repl writer worker 15] Failed command { drop: "system.profile" } on test with status IllegalOperation turn off profiling before dropping system.profile collection during oplog application I - [repl writer worker 15] Fatal Assertion 16359 I - [repl writer worker 15]
3.1.1 and 3.0.4-rc0
I COMMAND [repl writer worker 15] CMD: drop test.system.profile W REPL [repl writer worker 15] Failed command { drop: "system.profile" } on test with status IllegalOperation turn off profiling before dropping system.profile collection during oplog application
- is duplicated by
-
SERVER-14514 disallow convertToCapped on system collections
- Closed
- is related to
-
SERVER-18112 mongod replicates operations on system.profile collection
- Closed
-
SERVER-15207 Return errors from commands during replication
- Closed