Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-41451

Re-starting a secondary database in a replica set generates NetworkInterfaceExceededTimeLimit errors

    • Type: Icon: Question Question
    • Resolution: Community Answered
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.8
    • Component/s: Replication
    • None
    • Fully Compatible

      We have a replica set and the secondary and primary are in sync and all is good.

      After 7pm each evening we stop the secondary database instance, backup the server and then start it again. The secondary database instance then eventually catches up. This has worked for the last few months without any issues.

      Now, when the secondary database instance is restarted we get network timeout messages over and over again and the secondary gets further and further behind.

      We have no idea what causes these timeouts or how the timeout can be increased.

      Thanks

      Ian

      [^mongo log 28-05-2019.txt]

        1. diagnostics data - secondary 090719 V2.zip
          131.98 MB
        2. mongod - primary - 090719.log.zip
          44.80 MB
        3. mongod - secondary - 090719.log.zip
          984 kB
        4. primary-metrics-09072019.zip
          119.67 MB

            Assignee:
            dmitry.agranat@mongodb.com Dmitry Agranat
            Reporter:
            ihannah@meniscus.co.uk Ian Hannah
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: