[SERVER-18107] Crash on mongorestore with system.profile Created: 17/Apr/15  Updated: 19/Apr/15  Resolved: 17/Apr/15

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

Type: Bug Priority: Major - P3
Reporter: Chad Kreimendahl Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-18111 mongod allows user inserts into syste... Closed
duplicates SERVER-18112 mongod replicates operations on syste... Closed
duplicates TOOLS-717 mongorestore does not skip restore of... Closed
Operating System: ALL
Participants:

 Description   

When attempting to mongorestore from a mongobackup of a database that had a system.profile collection, an fassert is thrown and the secondary members of the replicaset crash.

Possibly consider a new option for mongorestore to ignore system.* files?



 Comments   
Comment by Chad Kreimendahl [ 19/Apr/15 ]

Thanks for turning that around so quickly. For reference to others who may find this:

We had an entirely fresh install of operating system with an entirely fresh and initial install of 3.0.2 from your aptitude packaging gateway. The backups were from a 2.6.9 system, being restored into the new 3.0.2 system. Thanks for the heads up on a workaround with 2.6.9 into 3.0.2

Comment by J Rassi [ 17/Apr/15 ]

Hi,

I am now able to reproduce this issue locally, so it is no longer necessary to provide the requested information. Thanks again for filing this ticket.

Over the course of my investigation, I have identified three underlying issues, and have filed tickets for each. I will therefore close this ticket as a duplicate of the following newly-created tickets:

  • TOOLS-717: mongorestore does not skip restore of system.profile collection. This is a regression that affects versions mongorestore versions 3.0.0 through 3.0.2.
  • SERVER-18111: mongod allows user inserts into system.profile collection. This is a regression that affects mongod versions 2.6.0 through 2.6.9 and versions 3.0.0 through 3.0.2.
  • SERVER-18112: mongod replicates operations on system.profile collection. This is an issue that has been fixed for 3.1.2 on the development branch by 1725d76f (SERVER-17573), but I am requesting backports to the v3.0 and v2.6 branches.

To work around this issue, please restore your backup with mongorestore 2.6.9.

Thanks again.
~ Jason Rassi

Comment by J Rassi [ 17/Apr/15 ]

Hi,

Sorry to hear that you encountered this problem. I have some follow-up questions to further this issue's diagnosis:

  • Can you confirm that when you observed this assertion failure, all members of your replica set were running mongod 3.0.2, and your restore process was run with mongorestore 3.0.2?
  • What version of mongod were you running when you took this backup? And, what version of mongodump did you use?
  • Would you be willing to compress the dump and upload it as an attachment to the ticket?

If you are not able to share the dump publicly (or the archive exceeds ~100MB in size), note also that you may upload it to a private server of ours that is accessible only to MongoDB staff members (hit "enter" at the password prompt):

scp -P 722 <file(s)> SERVER-18107@www.10gen.com:

Thanks.
~ Jason Rassi

Comment by Chad Kreimendahl [ 17/Apr/15 ]

Forgot to add the following: version 3.0.2

Comment by Chad Kreimendahl [ 17/Apr/15 ]

2015-04-17T15:39:45.212-0500 E REPL     [repl writer worker 10] writer worker caught exception:  :: caused by :: 10156 cannot update system collection: SomeDB.system.profile q: { _id: ObjectId('55316f8b82da779fbe6f4bd2') } u: { _id: ObjectId('55316f8b82da779fbe6f4bd2'), op: "command", ns: "SomeDB.$cmd", command: { mapreduce: "FGTiming", map: 

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