[SERVER-16817] --repair fails if there are multiple collections with outdated WT index versions Created: 13/Jan/15  Updated: 30/Jan/15  Resolved: 13/Jan/15

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Storage
Affects Version/s: None
Fix Version/s: 2.8.0-rc5

Type: Bug Priority: Blocker - P1
Reporter: Mathias Stearn Assignee: Mathias Stearn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Tested
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Comments   
Comment by Githook User [ 15/Jan/15 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: Better repair for WT

  • Doesn't construct RecordStores or indexes before they've been repaired
  • No longer need to skip checking index versions.
  • Updates numRecords and dataSize after the repair.

Related issues:
SERVER-16817 Skip checking index versions in WT during --repair
SERVER-16172 --repair fails before repairing collections in WT

A call to flushAllFiles is commented out due to SERVER-16869. Resolving it
should uncomment that line.
Branch: master
https://github.com/mongodb/mongo/commit/48deaff5bf31d21807c5dd7e7f5d313c7c96e8dc

Comment by Githook User [ 13/Jan/15 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-16817 Ignore WT index versions when starting with --repair
Branch: master
https://github.com/mongodb/mongo/commit/72089efb044ad1851a8c3fb1912edcaee759ba00

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