Shard Zones with Tiered Hardware

Ops and Admin Sharding
1

from this link : https://www.mongodb.com/docs/manual/tutorial/sharding-tiered-hardware-for-varying-slas/#scenario

I have some question, from this page setting shard key → { creation_date : 1 } 3 shards (1,2, 3) with 2 zones (“recent”, “archive”)

  1. zone “recent” → shard 1,2
  2. zone “archive” → shard 3
    Is it possible to evenly distribute incoming data between Shard 1 and Shard 2?
2

I don’t think using zones for sharding make any big difference regarding how the data is distributed. Basically Mongodb servers should try best to evenly distribute customer data between all available shards automatically. We, as clients/human/engineers, are not supposed to worry about it.