[DOCS-1351] Issues with keepalive section in diagnostics FAQ Created: 06/Apr/13  Updated: 30/Oct/23  Due: 22/May/15  Resolved: 05/Jun/15

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

Type: Task Priority: Major - P3
Reporter: J Rassi Assignee: Kay Kim (Inactive)
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: 6 years, 9 weeks ago

 Description   

The TCP keepalive section in the diagnostics FAQ suggests that users set tcp_keepalive_time system-wide to 5 minutes. It should be revised to reflect that, since version 2.0, the Linux build of the server automatically sets this on its own sockets (SERVER-3604). In addition, the following excerpt should be fact-checked and then rewritten (it's ambiguous as-is – take effect on existing connections? new connections?):

"The new tcp_keepalive_time value takes effect without requiring you to restart the mongod or mongos servers."



 Comments   
Comment by Githook User [ 13/Dec/17 ]

Author:

{'name': 'Tony Sansone', 'email': 'tony.sansone@mongodb.com', 'username': 'atsansone'}

Message: (DOCS-1351): Added prereq to editing deployments.
Branch: v3.4
https://github.com/10gen/mms-docs/commit/75c80f54e9544342b1c466a346af5b72cbaa2ee7

Comment by Githook User [ 13/Dec/17 ]

Author:

{'name': 'Tony Sansone', 'email': 'tony.sansone@mongodb.com', 'username': 'atsansone'}

Message: (DOCS-1351): Added prereq to editing deployments.
Branch: v3.6
https://github.com/10gen/mms-docs/commit/68f7a4d75d9b993010783bab7adbd892f9a9d8ad

Comment by Githook User [ 13/Dec/17 ]

Author:

{'name': 'Tony Sansone', 'email': 'tony.sansone@mongodb.com', 'username': 'atsansone'}

Message: (DOCS-1351): Added prereq to editing deployments.
Branch: master
https://github.com/10gen/mms-docs/commit/cecb2567f3aef7e6b0e76aefb481463702ba9b3e

Comment by Githook User [ 05/Jun/15 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-1351 keepalive
Branch: master
https://github.com/mongodb/docs/commit/9ccd932ea7ce9b7d94e4fe1c8dadae4fd389403c

Comment by Githook User [ 13/Mar/15 ]

Author:

{u'username': u'mpaik', u'name': u'Michael Paik', u'email': u'michael.paik@10gen.com'}

Message: DOCS-1351 with edits
Branch: master
https://github.com/mongodb/docs/commit/51e5883e6592b9d707d12d8d96bca7907cd71275

Comment by Githook User [ 13/Mar/15 ]

Author:

{u'username': u'mpaik', u'name': u'Michael Paik', u'email': u'michael.paik@10gen.com'}

Message: DOCS-1351 - updated keepalive info
Branch: master
https://github.com/mongodb/docs/commit/59d98e35a11574147392f74ace5a971fc8b98c42

Comment by Daniel Pasette (Inactive) [ 03/Jun/13 ]

The keep alive setting is only for connections created by a mongo[d|s] process. There is also the consideration of any client nodes in your cluster – I believe some drivers allow a keepalive setting as well.

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