[SERVER-21757] ServerStatus "advisoryHostFQDNs" should be optional and not default Created: 03/Dec/15  Updated: 04/Jan/17  Resolved: 24/Aug/16

Status: Closed
Project: Core Server
Component/s: Admin, Internal Code
Affects Version/s: 3.2.0-rc6
Fix Version/s: 3.3.12

Type: Improvement Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Jonathan Reams
Resolution: Done Votes: 0
Labels: bkp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Documented
is documented by DOCS-8939 ServerStatus "advisoryHostFQDNs" shou... Closed
Duplicate
is duplicated by SERVER-22026 Move advisoryFQDNs variable to its ow... Closed
Related
related to SERVER-20952 HostnameCanonicalizationWorker spams ... Closed
Backwards Compatibility: Minor Change
Backport Requested:
v3.2
Sprint: Platforms 2016-08-26
Participants:

 Description   

By using a ServerStatusSection this can be opt-in and we can also remove the specialized thread – HostnameCanonicalizationWorker.

If we really care about this not taking a long time we can find a way to add a timeout if needed – like by using a background-job (thread) with a timeout.



 Comments   
Comment by Githook User [ 24/Aug/16 ]

Author:

{u'username': u'jbreams', u'name': u'Jonathan Reams', u'email': u'jbreams@mongodb.com'}

Message: SERVER-21757 ServerStatus advisoryHostFQDNs should be optional
Branch: master
https://github.com/mongodb/mongo/commit/29189fc922f8746060e83ba27e46ba249eb3b9e4

Generated at Thu Feb 08 03:58:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.