[SERVER-30603] mongos shouldn't log the warning in the log when config server order isn't matching the configuration Created: 10/Aug/17 Updated: 27/Oct/23 Resolved: 11/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Andrey Brindeyev | Assignee: | Kaloian Manassiev |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding 2017-10-02 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently, if the config server's order in the mongos configuration doesn't match the configuration, the following warning message is logged:
Since the order of config servers insn't important for CSRS, the warning shouldn't be logged. |
| Comments |
| Comment by Kaloian Manassiev [ 11/Sep/17 ] |
|
Unfortunately, this warning is in place because of |