[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: |
|
||||||||
| 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: |