[SERVER-16552] notablescan breaks replication on mongorestore Created: 15/Dec/14  Updated: 22/Jan/15  Resolved: 22/Jan/15

Status: Closed
Project: Core Server
Component/s: Replication, Tools
Affects Version/s: 2.6.5
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Steffen Assignee: Ramon Fernandez Marina
Resolution: Incomplete Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

create a dump
restore this dump to a replicateset which has notablescan = true.

Participants:

 Description   

We have enable the notablescan feature in our replicaset.
When we no restore a dump of our data, the secondaries fail when they try to replicate the data from the dump.

 

2014-12-15T18:07:38.622+0000 [repl writer worker 1] ERROR: writer worker caught exception:  :: caused by :: 17243 could not get runner { _id: ObjectId('541999130cf27885358c926a') };  :: caused by ::
 error processing query: ns=database.collection limit=0 skip=0
Tree: _id == ObjectId('541999130cf27885358c926a')
Sort: {}
Proj: {}
 No query solutions on: { ts: Timestamp 1418666858000|2, h: -5089338154521627339, v: 2, op: "i", ns: "database.collection", o: { _id: ObjectId('541999130cf27885358c926a'), field = "value" } }
2014-12-15T18:07:38.622+0000 [repl writer worker 1] Fatal Assertion 18692

The secondaries fail everytime we start them again, since the retry the operation.
We need to disable notablescan = false to restore the dump.
After we have finished the resotre we can set notablescan = true again and no errors occur.



 Comments   
Comment by Ramon Fernandez Marina [ 22/Jan/15 ]

steffen, we haven't heard back from you for a while so we're closing this ticket. If this is still an issue for you please feel free to re-open and provide the information requested in my previous comment.

Thanks,
Ramón.

Comment by Ramon Fernandez Marina [ 08/Jan/15 ]

This looks very similar to SERVER-4718. Does your data contain a capped collection without an _id index?

Generated at Thu Feb 08 03:41:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.