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

get_last_error.js fails because it does not expect chaining to occur

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.8.0-rc2
    • Component/s: None
    • Labels:
      None
    • Operating System:
      ALL

      Description

      LOGS
      TASK HISTORY

       m31000| 2014-12-01T15:40:05.444+0000 I QUERY    [conn1] command test.$cmd command: getLastError { getlasterror: 1.0, w: 3.0, wtimeout: 1000.0 } keyUpdates:0  reslen:231 1001ms
      Trying w=3 with 2 nodes up, 1000ms timeout.
      {
      	"lastOp" : Timestamp(1417448404, 1),
      	"connectionId" : 1,
      	"n" : 0,
      	"syncMillis" : 0,
      	"waited" : 1001,
      	"wtimeout" : true,
      	"writtenTo" : [
      		"ip-10-13-142-105:31000"
      	],
      	"err" : "timeout",
      	"errmsg" : "timed out waiting for slaves",
      	"code" : 64,
      	"ok" : 1
      }
      assert: [1] != [2] are not equal : undefined
      Error: [1] != [2] are not equal : undefined
          at Error (<anonymous>)
          at doassert (src/mongo/shell/assert.js:11:14)
          at Function.assert.eq (src/mongo/shell/assert.js:38:5)
          at /data/mci/shell/src/jstests/gle/get_last_error.js:62:8

        Attachments

          Activity

            People

            Assignee:
            schwerin Andy Schwerin
            Reporter:
            ian.whalen Ian Whalen
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: