Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
*Location*: https://docs.mongodb.org/manual/reference/command/flushRouterConfig/#dbcmd.flushRouterConfig
*User-Agent*: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2646.0 Safari/537.36
*Referrer*: https://docs.mongodb.org/manual/reference/command/nav-sharding/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: reference/command/flushRouterConfig
*Location*: https://docs.mongodb.org/manual/reference/command/flushRouterConfig/#dbcmd.flushRouterConfig *User-Agent*: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2646.0 Safari/537.36 *Referrer*: https://docs.mongodb.org/manual/reference/command/nav-sharding/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: reference/command/flushRouterConfig
-
0.1
Description
Article does not mention that this must be run against the admin DB (unless this is what "is an administrative commnand" means). Also had to guess at the command format. I ran:
use admin;
|
db.runCommand({flushRouterConfig: 1})
|
and it seemed to work.