[SERVER-2421] Return FQDN of server in serverStatus, config.mongos and replSetStatus Created: 27/Jan/11  Updated: 29/May/17  Resolved: 14/Oct/15

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: 1.6.5
Fix Version/s: 3.2.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Adrien Mogenet Assignee: Spencer Jackson
Resolution: Done Votes: 6
Labels: mms-s
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
is documented by DOCS-9580 Docs for SERVER-2421: Return FQDN of ... Closed
Related
Backwards Compatibility: Fully Compatible
Sprint: Platform 2 04/24/15, Platform 6 07/17/15, Platform 7 08/10/15, Platform 9 (09/18/15), Platform A (10/09/15), Security B 10/30/15
Participants:

 Description   

It could be nice to explicitely give the fqdn of server when executing db.serverStatus().
It could be useful when connecting to remove hosts.



 Comments   
Comment by Spencer Jackson [ 14/Oct/15 ]

We should document the new field visible in serverStatus.

Comment by Githook User [ 14/Oct/15 ]

Author:

{u'username': u'spencerjackson', u'name': u'Spencer Jackson', u'email': u'spencer.jackson@mongodb.com'}

Message: SERVER-2421 SERVER-17739 Add FQDN canonicalization for serverStatus and SPNs
Branch: master
https://github.com/mongodb/mongo/commit/e7189d7af091983e9eedc1ca30bc7f1d8e136951

Comment by Andy Schwerin [ 06/Dec/14 ]

In many environments, the host's notion of its fqdn may not be the rest of the cluster's notion. This can be exacerbated if the nodes are referenced by DNS cnames, or if two anames refer to the same IP address or to the same host on different addresses.

I think to resolve this ticket in a way that satisfied automatic discovery might require some more constraints.

Comment by Cailin Nelson [ 06/Dec/14 ]

This ticket was Closed as Duplicate, however I don't believe the request was exactly fulfilled.

db.serverStatus().host does, indeed, return the hostname of the server on which the MongoDB process is running. However, the fqdn (hostname -f) is not returned.

It would be great if we could additionally return the FQDN in the following places:

  • db.serverStatus()
  • rs.status()
  • In the config.mongos collection

This would be quite valuable for MMS Monitoring auto-discovery. Currently, we sometimes have the problem that the Monitoring Agent cannot traverse a deployment because the non-qualified domain names exposed in these data sources are not accessible from the server hosting the Monitoring Agent. This is most frequently true for auto-discovery of mongos, but also comes up with auto-discovery of other nodes in a replica set.

Comment by Eliot Horowitz (Inactive) [ 27/Jan/11 ]

This was already added in 1.7.4 or so.

Generated at Thu Feb 08 02:59:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.