[SERVER-8367] Mongorestore doesn't report errors, even when running with a write concern Created: 29/Jan/13  Updated: 11/Jul/16  Resolved: 07/Feb/13

Status: Closed
Project: Core Server
Component/s: Tools
Affects Version/s: 2.2.2, 2.3.2
Fix Version/s: 2.4.0-rc1

Type: Improvement Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-8345 Change mongorestore default write con... Closed
Participants:

 Description   

Providing the --w option to mongorestore makes it call getLastError, but even if getLastError returns an error, we silently ignore that error and continue. We should at least log something, if not abort.



 Comments   
Comment by auto [ 07/Feb/13 ]

Author:

{u'date': u'2013-02-07T23:49:54Z', u'email': u'spencer@10gen.com', u'name': u'Spencer T Brody'}

Message: SERVER-8367 Log error messages from GLE during mongorestore
Branch: master
https://github.com/mongodb/mongo/commit/db1067156440d88b4c3dc9c187da55da47471d89

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