-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 5.0.0, 6.0.0, 6.3.0-rc0
-
Component/s: Sharding
-
Sharding NYC
-
Fully Compatible
-
ALL
-
v7.0, v6.3, v6.0, v5.0
-
Sharding NYC 2023-04-03, Sharding NYC 2023-04-17, Sharding NYC 2023-05-01, Sharding NYC 2023-05-15
-
3
Resharding will add documents to config.tags collection with the new temporary resharding namespace. But these docs, don't extend the zone range to encompass the entire sharding key pattern. The tag documents to be uploaded to config.tags are built here:
This function should be doing something similar to the resharding split policy (taking in the new resharding key and calling extend range on it) like this:
- is related to
-
SERVER-53432 Ensure that comparing resharding requested zones with the authoritative tags is protected by concurrency control
- Closed
-
SERVER-58433 ReshardingCoordinatorService Transaction In bumpCollectionVersionAndChangeMetadataInTxn Possibly Too Large
- Closed
- related to
-
SERVER-73848 Hashed shard keys with zones can cause issues with resharding
- Closed