[SERVER-35453] Print the IP address that the replica set hostname gets resolved to at startup Created: 06/Jun/18 Updated: 08/Jan/24 Resolved: 12/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking, Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
At startup we log the replica set config, which generally is specified in terms of hostnames. It would be nice to have a way to correlate incoming connections to what replica set member they came from. If at startup we printed the IP address(es) that we can resolve the hostname to, that could give us additional information that would be useful when reading customer log files. |
| Comments |
| Comment by Gregory McKeon (Inactive) [ 12/Jun/18 ] |
|
Closing because SERVER-35540 is a better approach. |
| Comment by Mira Carey [ 11/Jun/18 ] |
|
I opened SERVER-35540 to track possible work in moving more of our logging towards HostAndPort's, rather than in transport layer specific primitives. |
| Comment by Spencer Brody (Inactive) [ 11/Jun/18 ] |
|
mira.carey@mongodb.com, then can you just point us towards what we should use to get the resolved IP address from the hostname? |
| Comment by Gregory McKeon (Inactive) [ 11/Jun/18 ] |
|
spencer we think this is a replication feature - bouncing back to you to triage. |