[SERVER-5414] improve emergency recovery scripts Created: 26/Mar/12  Updated: 27/Feb/17  Resolved: 24/Feb/17

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

Type: Improvement Priority: Major - P3
Reporter: Greg Studer Assignee: Unassigned
Resolution: Incomplete Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-3698 When mongos reports config servers no... Closed
Participants:

 Description   

It would be nice to have better emergency scripts for :

1) Inferring chunk boundaries from data without config server info - ideally one that could make better guesses with any config server info we provide
2) Oplog recovery - not just replay but better tooling to traverse the oplog, find different kinds of ops, etc. It's hard to remember the format when under pressure.



 Comments   
Comment by Greg Studer [ 23/Apr/12 ]

To clarify, this ticket has three separate components (each of which may be a sub-issue when assigned)

  • better oplog replay
  • the analogous ability to replay a config.changelog against a stale config database to recover an up-to-date config database
  • better / more efficient script to infer chunk boundaries, or at minimum much more testing for the script
Comment by Greg Studer [ 26/Mar/12 ]

"changelog replay" might be a good first step...

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