[SERVER-10746] When config servers differ, report which config server the mongos trusted most recently Created: 11/Sep/13 Updated: 06/Dec/22 Resolved: 02/Jun/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
Followup from a conversation with Greg: when a mongos discovers that config servers differ, it could report the identity of the one whose data it has been considering as canonical. This would help direct users to figure out which config server to use for restoration, at least in some cases. |
| Comments |
| Comment by Andy Schwerin [ 02/Jun/16 ] |
|
This is not relevant after |