When repeatedly dropping a database and then creating a database with the same name in MongoDB 3.6, errors such as 'database does not exist' may occur during read-write operations or when dropping the database, as shown below:
Solution
This is a common issue that may arise if mongos has not refreshed its metadata cache. For more information, please refer to the official description as illustrated below:
There are two solutions; please choose one of them:
1. Restart mongos, which can be done in the Console Instance List.
2. Alternatively, run the flushRouterConfig command, which comes with a detailed explanation.
Was this page helpful?