|
some followup here RE: my investigation...
we prevent oplog application for {local, admin, config} db's here (via isOnInternalDb), and importing of the same db's here (tenant file importer service calls wiredTigerRollbackToStableAndGetMetadata which checks each ns with shouldImport)
I primarily referenced namespace string as a registry of used namespaces, but there appear to be some adhoc namespaces that are used that are not listed here (I found myself wishing for a mandatory central registry of all namespaces, perhaps with some sort of attached metadata that could be used in cases like this where we may or may not want to import entire databases, or import specific collections in a given database).
Based on this investigation, I'm not finding any namespaces that we are missing from import/oplog application. However, if a new collection that does need to be migrated is added at some point in the future, there is currently nothing to inform developers that additional work needs to be done for tenant migration support (these collections will simply be silently skipped).
|