[DOCS-11418] Operations Checklist not consistent with production notes on tcp keepalive Created: 06/Mar/18  Updated: 29/Oct/23  Resolved: 20/Mar/18

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

Type: Bug Priority: Minor - P4
Reporter: Eric Sommer Assignee: Allison Reinheimer Moore
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 5 years, 47 weeks, 1 day ago

 Description   

https://docs.mongodb.com/v3.4/administration/production-checklist-operations/

The TCP idle timeout on the Azure load balancer is 240 seconds by default, which can cause it to silently drop connections if the TCP keepalive on your Azure systems is greater than this value. You should set tcp_keepalive_time to 120 to ameliorate this problem.

https://docs.mongodb.com/manual/administration/production-notes/

The TCP idle timeout on the Azure load balancer is 240 seconds by default, which can cause it to silently drop connections if the TCP keepalive on your Azure systems is greater than this value. You should set tcp_keepalive_time to 120 to ameliorate this problem.

On Linux, mongod and mongos processes limit the keepalive to a maximum of 300 seconds (5 minutes) on their own sockets by overriding keepalive values greater than 5 minutes.

The former says 120. The latter says 120 for Azure, 300 for Linux. I believe the Production Notes are correct (120/300).



 Comments   
Comment by Allison Reinheimer Moore [ 20/Mar/18 ]

Change backported!

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