-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Critical - P2
-
Affects Version/s: None
-
Component/s: None
-
TAR 2025-05-26
-
2
-
Tools and Replicator
-
0.25
-
Not Needed
Problem Statement/Rationale
We have noticed a few tenant upgrades that failed to restore certain namespaces with ending newline characters. Newline characters are valid and should be able to be restored. Mongodump does recognize these collections and they are dumped as necessary but not the restore.
In the logs below, mongorestore thinks it is done but when comparing to the mongodump logs, we see that the collection ending with newlines were not restored and no logs indicate any attempt at restoring.
Example logs on atlas prod
Mongodump log: https://cloud.mongodb.com/admin/nds/serverlessDowngradeToFree/67b76767bbbab53a95647858/logs?logType=mongodump
Mongorestore log:
https://cloud.mongodb.com/admin/nds/serverlessDowngradeToFree/67b76767bbbab53a95647858/logs?logType=mongorestore
Steps to Reproduce
Create a collection that ends with a newline character and it should not be restored but it is dumped
Expected Results
All dumped db and collections to be restored
Actual Results
Collections with ending newline characters are not being restored
Additional Notes
This is blocking the completing of forced serverless to free migrations and could potentially become blocker for serverless to dedicated migrations
- is duplicated by
-
TOOLS-2978 Investigate mongorestore failure when restoring namespaces that include newlines
-
- Closed
-
- is related to
-
TOOLS-3895 List any skipped namespaces in mongorestore’s output.
-
- Needs Triage
-
-
TOOLS-3896 Avoid mongorestore's namespace-matching logic unless it's needed
-
- Needs Triage
-