[SERVER-22026] Move advisoryFQDNs variable to its own serverStatus section Created: 29/Dec/15  Updated: 29/Dec/15  Resolved: 29/Dec/15

Status: Closed
Project: Core Server
Component/s: Internal Code, Networking
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Spencer Jackson Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-21757 ServerStatus "advisoryHostFQDNs" shou... Closed
Related
related to SERVER-20952 HostnameCanonicalizationWorker spams ... Closed
Participants:

 Description   

Right now, the serverStatus entry which provides the canonicalized hostname is in the toplevel of the returned document. Obtaining the hostname can be slow, and serverStatus needs to return relatively quickly as it is polled by FTDC, so this field is obtained from a cache, populated by a separate thread. If advisoryFQDNs is moved to another serverStatus section, we could compute the value on request, and not need a background thread.



 Comments   
Comment by Scott Hernandez (Inactive) [ 29/Dec/15 ]

dup of SERVER-21757

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