Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
3.1.2
-
Query
-
Fully Compatible
-
ALL
-
-
Query 2017-03-27, Query 2017-04-17
Description
This bug is non-fatal in versions earlier than 3.1.2 (i.e., prior to the changes in SERVER-15207).
It requires the mapReduce to be performed on a special collection like "admin.system.roles" or "admin.system.users".
3.1.2+:
W ACCESS [repl writer worker 15] Skipping bad update to roles collection in oplog. NoSuchKey Missing expected field "role" Oplog entry: i
|
W ACCESS [repl writer worker 15] Skipping bad update to roles collection in oplog. NoSuchKey Missing expected field "role" Oplog entry: i
|
E REPL [repl writer worker 15] Failed command { create: "tmp.mr.system.roles_0", temp: true } on admin with status BadValue cannot write to 'admin.tmp.mr.system.roles_0' during oplog application
|
I - [repl writer worker 15] Fatal Assertion 16359
|
3.1.1 and 3.0.4:
W ACCESS [repl writer worker 15] Skipping bad update to roles collection in oplog. NoSuchKey Missing expected field "role" Oplog entry: i
|
W REPL [repl writer worker 15] Failed command { create: "tmp.mr.system.roles_0", temp: true } on admin with status BadValue cannot write to 'admin.tmp.mr.system.roles_0' during oplog application
|
I COMMAND [repl writer worker 15] CMD: drop admin.tmp.mr.system.roles_0
|
W REPL [repl writer worker 15] Failed command { drop: "tmp.mr.system.roles_0" } on admin with status UnknownError ns not found during oplog application
|
Attachments
Issue Links
- is duplicated by
-
SERVER-19435 mapreduce cause Secondary assert
-
- Closed
-
- is related to
-
SERVER-28074 Overly eager check for .system. in collection names causes error / assertion
-
- Closed
-
-
SERVER-15207 Return errors from commands during replication
-
- Closed
-