[SERVER-78000] Config server startup should handle shardIdentity with no clusterId Created: 12/Jun/23 Updated: 29/Oct/23 Resolved: 14/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 7.0.0-rc4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v7.0
|
||||||||||||
| Sprint: | Sharding NYC 2023-06-26 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Config server startup will initialize its sharding state if a shard identity document is found locally. This triggers loading cluster settings from the config server, including the cluster identity document, which is assumed to always be available if the shard identity was found, since it is always inserted earlier when the first config primary steps up. This logic runs before replication recovery, so if the config server restarts after a failed initial sync that only copied the shard identity document, there may be no cluster identity, which triggers an infinite retry loop looking for that document, blocking startup. |
| Comments |
| Comment by Githook User [ 15/Jun/23 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit e1e2dea21de4674f29c13ae2843c6822ac772b75) |
| Comment by Githook User [ 14/Jun/23 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |