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

dbhash_at_cluster_time.js fails with LockTimeout errors when running dbHash command on secondary

    • Fully Compatible
    • v4.0
    • TIG 2018-06-04
    • 58

      It is possible that the replication subsystem on the secondary is holding the global X lock when the mongo shell attempts to run the dbHash command. One option would be to retry the dbHash command as it should eventually succeed once the global X lock is released. Another option would be to wait for the secondary to have caught up to the primary as the oplog applier thread would then be idle.

      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.167+0000 2018-05-18T15:25:58.165+0000 E QUERY    [js] Error: command failed: {
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.167+0000 	"operationTime" : Timestamp(1526657158, 3),
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.167+0000 	"ok" : 0,
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.167+0000 	"errmsg" : "Unable to acquire lock '{2305843009213693953: Global, 1}' within a max lock request timeout of '0ms' milliseconds.",
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.167+0000 	"code" : 24,
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.167+0000 	"codeName" : "LockTimeout",
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.167+0000 	"$clusterTime" : {
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.167+0000 		"clusterTime" : Timestamp(1526657158, 3),
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.167+0000 		"signature" : {
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.167+0000 			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.167+0000 			"keyId" : NumberLong(0)
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.167+0000 		}
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.168+0000 	}
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.168+0000 } :
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.168+0000 _getErrorWithCode@src/mongo/shell/utils.js:25:13
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.168+0000 doassert@src/mongo/shell/assert.js:16:14
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.168+0000 _assertCommandWorked@src/mongo/shell/assert.js:516:17
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.168+0000 assert.commandWorked@src/mongo/shell/assert.js:600:16
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.168+0000 @jstests/replsets/dbhash_at_cluster_time.js:74:15
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.168+0000 @jstests/replsets/dbhash_at_cluster_time.js:4:2
      [js_test:dbhash_at_cluster_time] 2018-05-18T15:25:58.168+0000 failed to load: jstests/replsets/dbhash_at_cluster_time.js
      

            Assignee:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: