[SERVER-3698] When mongos reports config servers not in sync, also report which to sync from Created: 26/Aug/11 Updated: 20/Jul/15 Resolved: 20/Jul/15 |
|
| 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: | Unassigned |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
When a mongos reports that config servers are not in sync, it only prints 2 config servers' names and corresponding dbhashes. If it's possible to determine which config server's state is the correct one to use, it would be very helpful if the mongos could report this in its log messages. (If it's not possible to determine which config server's state is correct to use, then we need to at least document what to do to get out of this problem.) |
| Comments |
| Comment by Andy Schwerin [ 20/Jul/15 ] |
|
Obviated by |
| Comment by Richard Kreuter (Inactive) [ 26/Aug/11 ] |
|
Would obviate this issue. |