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

Restarting oplog query due to error: NetworkInterfaceExceededTimeLimit: error in fetcher batch callback: Operation timed out

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.8
    • Component/s: Replication
    • None
    • ALL
    • Hide

      1) standalone instance with ~40GB data

      2) setup initiate it as replica set, and play primary role

      3) add secondary machine into this replica set

      4) the secondary stuck in STARTUP2 for a few days.

      5) eventually secondary exit with a fatal error.

      Show
      1) standalone instance with ~40GB data 2) setup initiate it as replica set, and play primary role 3) add secondary machine into this replica set 4) the secondary stuck in STARTUP2 for a few days. 5) eventually secondary exit with a fatal error.

      Secondary node failed to sync data and crashed

       

      attached files include secondary mongod.log and diagnostic.data file. hope these helps

      my system is centOS 6 2Core CPU 4GB Ram

       

        1. mongod.log
          3.28 MB
        2. metrics.2018-10-30T01-09-14Z-00000
          1.10 MB

            Assignee:
            daniel.hatcher@mongodb.com Danny Hatcher (Inactive)
            Reporter:
            gen gen
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: