[SERVER-8449] Index build errors during mongod --repair swallowed, not reported. Created: 05/Feb/13  Updated: 10/Dec/14  Resolved: 02/Jun/13

Status: Closed
Project: Core Server
Component/s: Admin, Index Maintenance
Affects Version/s: 2.0.7, 2.2.3, 2.4.0-rc0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Andy Schwerin 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-8432 Mongod can fail to output error messa... Closed
Operating System: ALL
Participants:

 Description   

When an index build as part of a run of mongod --repair fails, the cleanup code that saves aside the last error information, drops indexes, and then restores the original last error value erroneously asserts that there is a last error object. The code is robust to there being no such object, and when run with --repair, there isn't one. In this case, the root cause of the index build failure will not be reported, leaving only a message such as the following (from v2.0.7):

Tue Feb  5 00:22:37 [initandlisten]  dbname Assertion failure le && !saveerrmsg.empty() db/pdfile.cpp 1724

Behavior not confirmed in 2.4 or 2.2, but code is similar to 2.0.



 Comments   
Comment by Daniel Pasette (Inactive) [ 02/Jun/13 ]

see: SERVER-8432

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