fix(replset): correct legacy max staleness calculation

We were calculating lastUpdateTime using nanoseconds instead of milliseconds, despite calculating maxStaleness with a millisecond lastWriteDate
mongodb · Aug 13, 2019 · 2eab8aa · 2eab8aa
1 parent 9c5c928
commit 2eab8aa
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/lib/core/topologies/replset.js b/lib/core/topologies/replset.js
@@ -415,10 +415,10 @@ var pingServer = function(self, server, cb) {
 
       // Calculate latency
       var latencyMS = new Date().getTime() - start;
+
       // Set the last updatedTime
-      var hrTime = process.hrtime();
-      // Calculate the last update time
-      server.lastUpdateTime = hrTime[0] * 1000 + Math.round(hrTime[1] / 1000);
+      var hrtime = process.hrtime();
+      server.lastUpdateTime = (hrtime[0] * 1e9 + hrtime[1]) / 1e6;
 
       // We had an error, remove it from the state
       if (err) {