Change namespace option on mongomirror
I was wondering why you can migrate data but you actually (as far I as saw) cannot change the database name during the process of migration (not using mongod/mongorestore unix/win commands but Atlas directly).
From the technical support:
"This is because Live Migration using mongomirror as an underlying process, which in this case tails the oplog and recreates the data exactly as is. This tool is typically used to minimize downtime, especially in production environments, for users who are migrating their data as is while writes are still occurring on the source instance. "
However, as I responded:
"Ok thanks for your message. Ok interesting point about the downtime but don't you think that it could be at least optional, but with a warning?
For my use case (and I don't think I might be the only one), We have Prod/PreProd/Dev environments and sometimes, a cluster can contains the same database with different namespace for different tests. Because I cannot change the name space, either I have to do it from mongo restore, either I have to run my tests one by one and run the migration after each tests"
Upvote if you're interested by this option!
Maxime
shared this idea
-
Kyle
commented
Agreed, we really need the ability to rename databases via mongomirror. Without it, we have to use mongodump/mongorestore which is really slow for decent sized databases.
-
Benjamin
commented
Hi here, we are using mongomirror for live migrations but this tool really lack the possibility of renaming a database during migration.
+1 for implementing database name conversion in mongomirror and live migration.