According to docs, documents with different partitionKey
may end up in same partition but documents with same partitionKey
are guaranteed to end up in same partition.
Now, lets consider a case where you have partitionKey
with cardinality=100
(for example 100 tenants).
Initially, all data is roughly equally distributed across partitions.
Lety say you end up with partitions of about 50GB size. I would assume in that case you might have a few partition keys contained within same partition. Then, all of the sudden your 2 tenants grow exponentially and they go to 200GB size.
Since partition have 250GB limit, now you're in problem.
Questions:
- How is this being solved?
- Is DocumentDB partitioning handling this moving to separate partitions?
- Should we (and are we even able to) view data/storage consumption per partitionKey (not partition)?
If someone could shed a bit of light to these dilemas as i couldnt find answers to these specific questions in docs.