Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 9.0.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Cluster Scalability
Backwards Compatibility:
Fully Compatible
Sprint:
ClusterScalability 27Apr-11May, ClusterScalability 11May-25May
Linked BF Score:
200
Story Points:
3
CAR Domain/s:
None

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

Under SPM-3978, participant shards learn about resharding via explicit commands in all stages instead of shard-version refreshes that read reshardingFields. Once those commands are in place, the coordinator's reshardingFields writes on config.collections are redundant.

When featureFlagReshardingNoRefreshApplyingAndBlockingWrites is enabled, gate off the coordinator's writes to reshardingFields.

depends on

SERVER-92437 Problems with resharding operation that starts while the FCV is "8.0" or "7.3" and commits while the FCV is "Downgrading to 7.0"

Open

SERVER-118957 Remove Feature Flag for SPM-3978

Backlog

is related to

SERVER-92437 Problems with resharding operation that starts while the FCV is "8.0" or "7.3" and commits while the FCV is "Downgrading to 7.0"

Open

SERVER-124256 Integrate _shardsvrReshardDonorCriticalSectionStarted with coordinator

Closed

related to

SERVER-127298 Update hot_backups test to honor featureFlagReshardingInitNoRefresh

Closed

Assignee:: Abdul Qadeer
Reporter:: Abdul Qadeer
Participants:: Abdul Qadeer, Githook User
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Apr 28 2026 10:19:47 PM UTC
Updated:: May 20 2026 09:41:36 PM UTC
Resolved:: May 19 2026 08:28:51 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates