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

Cannot read property 'clusterTime' of undefined

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Critical - P2 Critical - P2
    • 3.6.7
    • Affects Version/s: 3.6.6
    • Component/s: Core
    • Not Needed

      When making a rolling restart of my Atlas cluster, this error is sometimes thrown when the client looses or re-establishes the connection, not sure.

      Can this be handled gracefully by adding further if-checks?

      Error message: "Cannot read property 'clusterTime' of undefined"
      [https://github.com/mongodb/node-mongodb-native/blob/3.6/lib/core/wireprotocol/command.js#L53|This line causes the error]

      Stack trace from NODE-3202: 

      TypeError: Cannot read property 'clusterTime' of undefined
    at _command (/service/node_modules/mongodb/lib/core/wireprotocol/command.js:53:63)
    at command (/service/node_modules/mongodb/lib/core/wireprotocol/command.js:28:5)
    at Object.getMore (/service/node_modules/mongodb/lib/core/wireprotocol/get_more.js:92:3)
    at Connection.getMore (/service/node_modules/mongodb/lib/cmap/connection.js:179:8)
    at /service/node_modules/mongodb/lib/core/sdam/server.js:333:12
    at Object.callback (/service/node_modules/mongodb/lib/cmap/connection_pool.js:345:7)
    at processWaitQueue (/service/node_modules/mongodb/lib/cmap/connection_pool.js:468:23)
    at /service/node_modules/mongodb/lib/cmap/connection_pool.js:236:28
    at processTicksAndRejections (internal/process/task_queues.js:75:11)

            Assignee:
            neal.beeken@mongodb.com Neal Beeken
            Reporter:
            admin@bicrypt.net Maximilian Schagginger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: