[SERVER-346] --notablescan doesn't work with replication Created: 09/Oct/09  Updated: 12/Jul/16  Resolved: 16/Oct/09

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 1.1.2

Type: Bug Priority: Major - P3
Reporter: Dwight Merriman Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

i am not sure why this is a table scan - does the _id index not yet exist because the collection "test.foo" was brand new here? this is on a slave running --notablescan:

Fri Oct 9 13:41:58 repl: sleep 2sec before next pass
Fri Oct 9 13:42:00 repl: main@localhost:27017
Fri Oct 9 13:42:00 User Exception table scans not allowed
Fri Oct 9 13:42:00 Assertion: table scans not allowed
Fri Oct 9 13:42:00 sync: caught db exception massert:table scans not allowed while applying op: { ts: Timestamp 1255110118000|1, op: "i", ns: "test.foo", o:

{ _id: ObjId(4acf75e64848d17fb707151c), x: 33.0 }

}
Fri Oct 9 13:42:00 repl: applied 1 operations
Fri Oct 9 13:42:00 repl: end sync_pullOpLog syncedTo: Fri Oct 9 13:41:58 2009 4acf75e6:1
Fri Oct 9 13:42:00 repl: sleep 1sec before next pass
Fri Oct 9 13:42:01 repl: main@localhost:27017



 Comments   
Comment by Eliot Horowitz (Inactive) [ 16/Oct/09 ]

release 10/16/2009

Generated at Thu Feb 08 02:53:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.