We use Mongodb 2.4.6
We added a new shard to our cluster. Each shard is a replica set with 3 nodes (2 powerful nodes and one backup hidden secondary)
We use tag aware sharding.
The new shard was added to a collection which was on 2 shards only before. So the data was balanced from 2 old nodes to the new one. 3 in total for this collection. Chunk size per shard is now equal (1172 each). On these shards there is only one collection (tag aware sharding).
But on one of the 2 old shards we see a lot cleanup messages in the log, thus we have high IO on this server
It seems the the cleaner goes through the whole hashed shard key range.
1. Is there a way to skip this cleanup with compaction, repair or full resync?
We also disabled "_secondaryThrottle" afterwards on the balancer setting, but it seems that this is not recognized on the replicaset
2. Is there a way to disable it afterwards?