As per today we are ensuring that a user isn't allowed to enable both chunk autosplit and defragmentation on a collection within the context of a single configureCollectionAutoSplitter command (as the concurrent execution of these two processes may produce conflicting operations).

Nevertheless, there are more complex interactions that may lead to such undesired state (e.g. a sequence of two configureCollectionAutoSplitter requests, the first enabling autosplit, the second one requesting for defragmentation) which are currently unmanaged: the most recent request should instead cause the execution of the conflicting process to be stopped.

In addition to this, the completion of the chunk defragmentation process should trigger the re-activation of the autosplit process on the affected collection.