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