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

TCP keepalive options in MongoDB Diagnostics FAQ

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Needs Triage
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: mongodb-3.4.1
    • Fix Version/s: None
    • Component/s: manual
    • Labels:
      None
    • Environment:
      3.4.1 sharded cluster, Redhat Linux 7

      Description

      The Diagnostics section indicates that the TCP keep alive setting should be the same for all components. While settings for the mongoD process should be consistent across all nodes, it is possible to have a different setting on mongoS and or client machines.

      This is not clear from the Diagnostic section of the documentation as it stands.

      If your MongoDB deployment experiences keepalive-related issues, you must alter the keep alive value on all machines hosting MongoDB processes. This includes all machines hosting mongos or mongod processes and all machines hosting client processes that connect to MongoDB.

      This statement reads that the keep alive value must be identical on all mongoS, mongoD, and client machines.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            annette.morrissey Annette Morrissey (Inactive)
            Participants:
            Last commenter:
            Anthony Sansone Anthony Sansone
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Days since reply:
              4 years, 46 weeks, 5 days ago
              Date of 1st Reply: