[SERVER-59384] Should provide ability to perform periodic DNS health checks Created: 16/Aug/21 Updated: 29/Oct/23 Resolved: 03/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Lamont Nelson | Assignee: | Kshitij Gupta |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-2364-faulty-mongos | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v5.0
|
||||||||||||||||
| Sprint: | Sharding 2021-11-29, Sharding 2021-12-13, Sharding 2021-12-27, Sharding 2022-01-10, Sharding 2022-01-24, Sharding 2022-02-07 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 178 | ||||||||||||||||
| Story Points: | 3 | ||||||||||||||||
| Description |
We need to build a representative list of servers to test. This might be tricky of somehow we pick servers that actually do have incorrect DNS name, and we treat it as a fatal error. A simple solution: Remember it's important to always cap the list of servers we resolve, we need to control the cost. |
| Comments |
| Comment by Githook User [ 14/Mar/22 ] |
|
Author: {'name': 'Kshitij Gupta', 'email': 'kshitij.gupta@mongodb.com', 'username': 'kshitijng'}Message: (cherry picked from commit 1d8aaed7f9286ce90317d03fc1815bb58b43e31d) |
| Comment by Githook User [ 14/Mar/22 ] |
|
Author: {'name': 'Andrew Shuvalov', 'email': 'andrew.shuvalov@mongodb.com', 'username': 'shuvalov-mdb'}Message: |
| Comment by Githook User [ 03/Feb/22 ] |
|
Author: {'name': 'Kshitij Gupta', 'email': 'kshitij.gupta@mongodb.com', 'username': 'kshitijng'}Message: |
| Comment by Githook User [ 03/Feb/22 ] |
|
Author: {'name': 'Kshitij Gupta', 'email': 'kshitij.gupta@mongodb.com', 'username': 'kshitijng'}Message: |