Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-11418

Operations Checklist not consistent with production notes on tcp keepalive

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Last comment by Customer:
      true
    • Sprint:
      KANBAN BUCKET

      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).

        Attachments

          Activity

            People

            Assignee:
            allison.moore Allison Reinheimer Moore
            Reporter:
            eric.sommer Eric Sommer
            Participants:
            Last commenter:
            Allison Reinheimer Moore Allison Reinheimer Moore
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Days since reply:
              3 years, 31 weeks, 5 days ago
              Date of 1st Reply: