[SERVER-47552] Unable to do point in time recovery using oplogReplay - Created: 15/Apr/20 Updated: 16/Apr/20 Resolved: 15/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Satvant Singh | Assignee: | Carl Champain (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Step 1: mongorestore --port 27017 --nsInclude mydb1.mycoll ./ --drop Step 2: mongorestore --port 27017 --oplogReplay --oplogLimit 1586934385 ./ |
| Participants: |
| Description |
I dropped "mydb.mycoll" earlier which is not require to me. |
| Comments |
| Comment by Carl Champain (Inactive) [ 15/Apr/20 ] |
|
The error cannot apply insert or update operation on a non-existent namespace ... is typically the result of trying to do an oplog apply operation on top of an incomplete backup. The namespace in question was not part of the backup, thus the oplog apply operation complains that it was told to do some operation on a non-existent data. That said, the SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to be a bug, I will now close it. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the MongoDB Community Forums or on Stack Overflow with the mongodb tag. Kind regards,
|