[SERVER-79109] Expose a future that becomes ready when auto-bootstrapped is finished Created: 19/Jul/23  Updated: 29/Oct/23  Resolved: 22/Sep/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: Wenqin Ye
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-80010 Router role should wait for auto-boot... Backlog
Assigned Teams:
Sharding NYC
Backwards Compatibility: Fully Compatible
Sprint: Sharding NYC 2023-09-04, Sharding NYC 2023-09-18, Sharding NYC 2023-10-02
Participants:

 Description   

This is mainly for the router role to know when to start accepting connections. For both config server primaries and secondaries, the auto bootstrap is considered finished when there's at least one shard in the cluster (the config shard). For shard servers, it is considered finished when the replication transitions to at least secondary.



 Comments   
Comment by Githook User [ 22/Sep/23 ]

Author:

{'name': 'wenqinYe', 'email': 'wenqin908@gmail.com', 'username': 'wenqinYe'}

Message: SERVER-79109: Expose a future that becomes ready when auto-bootstrapped is finished
Branch: master
https://github.com/mongodb/mongo/commit/09ecabb75a6d6962432f2d8687f2f0d870644bb2

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