Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- resharding-improvements
- resharding-multiversion-improvements

Assigned Teams:

Cluster Scalability
Backwards Compatibility:
Fully Compatible
Sprint:
ClusterScalability Nov10-Nov24, ClusterScalability Nov24-Dec8
Linked BF Score:
200
Story Points:
4
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Multiple new fields have been added to the reshardCollection command since 8.0. We should add a test to verify that these fields are appended or not appended correctly based on the FCV in the downstream _shardsvr and _configsvr commands and the state documents, such that the PrimaryOnlyService join condition (e.g. here) is handled correctly.

blocks

SERVER-99745 Make hashed shard key index optional upon sharding and resharding a collection

Needs Merge

is related to

SERVER-96843 core_sharding tests that run non-retryable commands shouldn't run in suites with stepdowns

Closed

related to

SERVER-114426 reshard_collection_basic.js fails in burn_in:sharded_retryable_writes_downgrade suites on implicit multiversion {A,UB}SAN variants

Backlog

SERVER-91802 Make hashed shard key index optional upon sharding the collection

Closed

SERVER-91975 Allow reshardCollection() to not require the hashed index for hashed shard keys

Closed

Assignee:: Natalie Hill
Reporter:: Cheahuychou Mao
Participants:: Cheahuychou Mao, Githook User, Natalie Hill
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Jan 09 2025 05:33:58 PM UTC
Updated:: Nov 26 2025 06:26:28 PM UTC
Resolved:: Nov 26 2025 06:25:16 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates