Open
Description
In the current implementation, shard metadata is not stored within shard's range, e.g. consider a KV data storage with a fixed range, there is currently no mechanism to ensure its related metadata is stored within that fixed key range.
Need to check whether this is going to cause any problem.