Starting in 8.0, the filtering metadata refresh during shardCollection is performed outside the critical section in a best effort way to avoid holding the critical section while talking to the config server. Therefore, it is possible for the filtering metadata to still be unknown when the transaction below starts. Given this, perform a find to trigger a filtering metadata refresh to prevent the transaction from hitting a StaleConfig error.
Please note that this test has been removed from 8.1+ by SERVER-68131.
- is related to
-
SERVER-68131 Remove Feature Flag for PM-1632
-
- Closed
-