A schema operation requires exclusive access. If compaction is already running on that table, the schema operation cannot be executed and EBUSY is returned to the caller. An interesting scenario is when the application tries to drop a collection that is being compacted, compaction is probably not worth pursuing and should be interrupted.

This ticket should investigate how we could address this kind of scenario.