[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: |
|
||||
| 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 (
|
| Comments |
| Comment by Githook User [ 13/Dec/17 ] |
|
Author: {'name': 'Tony Sansone', 'email': 'tony.sansone@mongodb.com', 'username': 'atsansone'}Message: ( |
| Comment by Githook User [ 13/Dec/17 ] |
|
Author: {'name': 'Tony Sansone', 'email': 'tony.sansone@mongodb.com', 'username': 'atsansone'}Message: ( |
| Comment by Githook User [ 13/Dec/17 ] |
|
Author: {'name': 'Tony Sansone', 'email': 'tony.sansone@mongodb.com', 'username': 'atsansone'}Message: ( |
| 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: |
| 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: |
| 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: |
| 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. |