[DOCS-2327] Altering TCP keepalive Created: 29/Nov/13  Updated: 30/Oct/23  Resolved: 13/Mar/15

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

Type: Task Priority: Major - P3
Reporter: Nick Pellant Assignee: Michael Paik
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 10 years, 11 weeks, 5 days ago

 Description   

Page: http://docs.mongodb.org/manual/faq/diagnostics/#does-tcp-keepalive-time-affect-sharded-clusters-and-replica-sets

We currently show the ability to edit the Linux tcp keepalive via the /proc/ method, which won't survive a reboot of the server. We should also document how to make a more permanent TCP keepalive alteration via the sysctl method.



 Comments   
Comment by Adam Comerford [ 29/Nov/13 ]

I think the variance in terms of how to make this permanent (depending on your distro) is the reason for this note:

The new tcp_keepalive_time value takes effect without requiring you to restart the mongod or mongos servers. When you reboot or restart your system you will need to set the new tcp_keepalive_time value, or see your operating system’s documentation for setting the TCP keepalive value persistently.

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