Currently, when a shard replica set is reconfigured to add or remove nodes, all mongoses monitoring that set will detect the change and each one will attempt to update the seed list for that set that is stored on the config servers. This means all the mongoses are racing to do the update, performing duplicate and unnecessary work and network traffic. Instead, the primary of the set being reconfigured should be the sole party responsible for updating the configuration stored on the config servers.