[DOCS-6071] TCP Keepalive on EC2 recommendation Created: 19/Aug/15  Updated: 30/Oct/23  Resolved: 13/Mar/23

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

Type: Bug Priority: Critical - P2
Reporter: Jason Mimick (Inactive) Assignee: Alison Huh
Resolution: Done Votes: 0
Labels: docs-mongodb-ec2, reopened, triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 48 weeks, 6 days ago

 Description   

We usually recommend cranking the TCP KeepAlive at 120, yet this doc on EC2 recommends 300: http://docs.mongodb.org/ecosystem/platforms/amazon-ec2/#keepalive



 Comments   
Comment by Alison Huh [ 02/Mar/23 ]

Perfect, thanks for the clarification john.murphy@mongodb.com!

Comment by John Murphy [ 02/Mar/23 ]

Hi alison.huh@mongodb.com

1. 120 is the recommended setting across all cloud providers.
2. This section in the docs is still valid. We accept up to 5 minutes, even if it won't effectively do anything useful. The recommended setting to make keep alives useful is 2 minutes.

Comment by Alison Huh [ 23/Feb/23 ]

Hi john.murphy@mongodb.com, I know this original ticket just mentions EC2, but I had two follow-up questions regarding this before I start editing/adding information on the docs: 

  1. Is 120 a recommendation we're making across all VMs or is this just specific to EC2?
  2. I'm seeing that in the docs, it currently says: 

    Keepalive values greater than 300 seconds, (5 minutes) will be overridden on mongod and mongos sockets and set to 300 seconds.

Does this recommendation still hold up or is this supposed to be changed to 120 seconds as well?

Comment by Sarah Olson [ 03/Nov/22 ]

Thanks for the confirm john.murphy@mongodb.com 

Comment by John Murphy [ 03/Nov/22 ]

We still need to make sure all our publicly facing documentation has a consistent recommendation of 120.

Comment by Education Bot [ 01/Nov/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!

Comment by Jason Mimick (Inactive) [ 21/Aug/15 ]

dean.johnson - good idea, done.

Comment by Dean Johnson [ 20/Aug/15 ]

If the EC2 recommendation in the docs has change, would a DOCS jira ticket be in order?

Comment by Jason Mimick (Inactive) [ 19/Aug/15 ]

Thanks james.tan - that's what I was thinking, but wanted to double check before telling a customer.

Comment by James Tan [ 19/Aug/15 ]

IIRC our EC2 recommendation (300) is outdated.

Comment by Jason Mimick (Inactive) [ 19/Aug/15 ]

'we' as in MongoDB official documentation; http://docs.mongodb.org/manual/faq/diagnostics/#does-tcp-keepalive-time-affect-mongodb-deployments.

Comment by Alexander Komyagin [ 19/Aug/15 ]

I'm also curious where do both numbers come from. The default connection timeout for ELB's is still 60 seconds according to this: https://aws.amazon.com/blogs/aws/elb-idle-timeout-control/

Comment by Alexander Komyagin [ 19/Aug/15 ]

Who are "we" ?

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