too many connections to a mongod instance will botch performance

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Incomplete
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Networking
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In some workloads, there are a lot of connections to one or many mongod instances which run as a shard. We then start getting these errors in dmesg:
      TCP: request_sock_TCP: Possible SYN flooding on port 10105. Sending cookies. Check SNMP counters.
      TCP: request_sock_TCP: Possible SYN flooding on port 10104. Sending cookies. Check SNMP counters.

      After the workload is gone, the mongod instance responds very slowly to some very simple queries. If we restart the mongod instances, the problem goes away. We have increased somax, tcp syn backlog, and tcp memory (rmem, wmem), but the issue is not fixed. Is this old ticket still related?

      https://jira.mongodb.org/browse/SERVER-2554

      Thank you

            Assignee:
            Mark Agarunov (Inactive)
            Reporter:
            Tudor Aursulesei
            Votes:
            1 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: