[DOCS-13440] Investigate changes in SERVER-45304: Include resolved IP address in rs.status() Created: 21/Feb/20 Updated: 30/Oct/23 Resolved: 27/Feb/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 3 years, 50 weeks, 2 days ago | ||||||||||||||||
| Epic Link: | DOCS: 4.4 Server Release Work | ||||||||||||||||
| Description |
DescriptionDownstream Change Summary A new field (IP address) is introduced to the rs.status() and rs.conf() output, which shows the resolved IP address for the members of the replica-set. The field is missing prior a successful DNS lookup (which happens asynchronously). See # Description of Linked Ticket Same as Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Ravind Kumar (Inactive) [ 24/Feb/20 ] |
|
So there are three things we need to consider here:
|