We recently discovered that dataSize command doesn't yield while scanning the index. This means that during its execution it will possibly block all the operations that requires exclusive access to the collection and considering that scanning the index for the entire collection can take long time this could have a huge impact on the customer workload.

Recently (SERVER-58356) we changed the yield policy to be  INTERRUPT_ONLY so that we can at least kill the operation if needed.

The goal of this ticket to change the yielding policy to YIELD_AUTO for both when the command is called with estimate:true or false