[SERVER-83305] Make sharding repl set aware service no-op on stepup Created: 15/Nov/23  Updated: 07/Dec/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-83302 Don't automatically initialize shardi... Backlog
Related
is related to SERVER-82965 [After v8.0] Remove backwards compabi... Needs Scheduling
Assigned Teams:
Cluster Scalability
Participants:

 Description   

when sharding state is not enabled. This ticket is referring to these services



 Comments   
Comment by Randolph Tan [ 07/Dec/23 ]

Update: most of the services that does could access uninitialized sharding component or have actual side effects were already made idle in SERVER-83376. The only service left is the balancer.

Generated at Thu Feb 08 06:51:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.