The balancer in testshard1.js is turned on to mimic a client enviroment where aggregations are issued concurrently with balancing. More recently the balancer was changed in a way that sometimes left the cluster with all chunks on one shard, which exposed some assertions in this test that depend on a particular data distribution. Such assertions are not appropriate for this test and should instead construct their own cluster which matches their assumptions.