[DOCS-6314] We should recommend CNAME's TTL to be set to zero Created: 02/Oct/15  Updated: 30/Oct/23  Resolved: 27/Sep/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Dmitry Ryabtsev Assignee: Kay Kim (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 8 years, 19 weeks, 6 days ago
Epic Link: DOCSP-1769

 Description   

With three config servers set up it is possible to have a scenario when after CNAME change connections to config servers established incorrectly. For example, mongos, instead of connecting to the config servers #1, #2 and #3 may have two connections to the config server #1, none to #2 and one to #3. That may be caused by a non-zero TTL value set for a CNAME record used to host a config server. This article should contain a recommendation to have CNAME's TTL set to zero.


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