[DOCS-9779] TCP keepalive options in MongoDB Diagnostics FAQ Created: 16/Jan/17  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: mongodb-3.4.1
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Annette Morrissey (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

3.4.1 sharded cluster, Redhat Linux 7


Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

The Diagnostics section indicates that the TCP keep alive setting should be the same for all components. While settings for the mongoD process should be consistent across all nodes, it is possible to have a different setting on mongoS and or client machines.

This is not clear from the Diagnostic section of the documentation as it stands.

If your MongoDB deployment experiences keepalive-related issues, you must alter the keep alive value on all machines hosting MongoDB processes. This includes all machines hosting mongos or mongod processes and all machines hosting client processes that connect to MongoDB.

This statement reads that the keep alive value must be identical on all mongoS, mongoD, and client machines.



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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