The sharding_ddl_util::removeQueryAnalyzerMetadataFromConfig() is currently only called in sharded collection path. So the dropDatabase command currently doesn't delete the config.queryAnalyzers docs for unsharded collections. There was a bug in the jstest added in SERVER-69150. It wasn't verifying the config.queryAnalyzers doc is deleted so we failed to catch that.
- causes
-
SERVER-94648 Query analyzer drop during dropCollection should attach session information
- Closed
- is duplicated by
-
SERVER-73990 Make query analysis work with collection renaming
- Closed
- related to
-
SERVER-76296 Make sure query sampling works correctly after DDL operations
- Closed