Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-1083

MongoError: connection 569 to <Secondary node> timed out

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 2.2.32
    • Affects Version/s: 2.2.29
    • Component/s: MongoDB 3.2
    • Environment:
      Production

      Our API got the error as below, but current Primary is another node, please check it that relate about a bug that has been fixed in 2.2.30 or not.

      2017-07-18T06:46:40.372Zerr : MongoError: connection 569 to <Secondary Node>:27017 timed out while storing pending status for execution ID : xxxxxxxxxxxxxxxx
      2017-07-18T06:46:40Z,CRITICAL,CTAS,cta-api,An uncaughtException was found : ReferenceError: err is not defined
      at Pool.destroy (/compass/test/app/cta-api/node_modules/mongodb-core/lib/connection/pool.js:867:27)
      at Connection. (/compass/test/app/cta-api/node_modules/mongodb-core/lib/connection/pool.js:265:14)
      at Connection.g (events.js:291:16)
      at emitTwo (events.js:106:13)
      at Connection.emit (events.js:191:7)
      at Socket. (/compass/test/app/cta-api/node_modules/mongodb-core/lib/connection/connection.js:197:10)
      at Socket.g (events.js:291:16)
      at emitNone (events.js:86:13)
      at Socket.emit (events.js:185:7)
      at Socket._onTimeout (net.js:339:8)
      at ontimeout (timers.js:365:14)
      at tryOnTimeout (timers.js:237:5)
      at Timer.listOnTimeout (timers.js:207:5)
      

            Assignee:
            matt.broadstone@mongodb.com Matt Broadstone
            Reporter:
            jongchana.phuwasate JONGCHANA PHUWASATE
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: