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:
None

Assigned Teams:

Catalog and Routing
Backwards Compatibility:
Fully Compatible
Sprint:
CAR Team 2025-11-24, CAR Team 2025-12-08
Story Points:
2
CAR Domain/s:
None

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

~~SERVER-112658~~ migrated existing logic to enable/disable sharding subsystem to ShardingInitializationMongoD class, a ReplicaSetAwareService that sets no guarantees in the execution order of its onStepUp()/opStepDown() against other instances. Although this is OK today, it leaves the door to potential future regressions.

The objective of this ticket is to revisit the set of existing ReplicaSetAwareServices and sets the proper prerequisites that could prevent such a scenario.

is related to

SERVER-112658 Extract functions to manage the Sharding subsystem on stepup/down from ReplicationCoordinatorExternalStateImpl

Closed

related to

SERVER-114062 ReplicaSetAwareServiceRegistry calls services in the wrong order if there are dependencies

Open

SERVER-114562 PrimaryOnlyService doesn't let services to specify their dependencies

Backlog

Assignee:: Jordi Olivares Provencio
Reporter:: Paolo Polato
Participants:: Githook User, Jordi Olivares Provencio, Paolo Polato
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Oct 24 2025 08:44:44 AM UTC
Updated:: Dec 03 2025 03:52:02 PM UTC
Resolved:: Dec 03 2025 03:52:02 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates