As described in MXS-4214, there's a need to have finer control over when the schemarouter caches are emptied as the act of populating the cache causes a one-time increase in query latency.

Being able to manually clear the cache, both globally and for a single user, would make it easier to manage when the expensive work of loading the database and table information takes place.