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

Spurious WriteConflict error with multi-statement transactions

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • 3.7.4
    • Storage
    • None
    • Replication
    • ALL

    Description

          ses = db.getMongo().startSession()
          dbs = ses.getDatabase("test")
       
          printjson(dbs.createCollection("c", {writeConcern: {w: "majority"}}))
       
          print("TRANSACTION 1")
          printjson(ses.startTransaction())
          printjson(dbs.c.insert({_id: 0}))
          printjson(ses.commitTransaction())
       
          print("TRANSACTION 2")
          printjson(ses.startTransaction())
          printjson(dbs.c.insert({_id: 1}))
          printjson(ses.commitTransaction())
      

      The second transaction fails with

      assert: command failed: {
      	"operationTime" : Timestamp(1524048246, 2),
      	"ok" : 0,
      	"errmsg" : "WriteConflict",
      	"code" : 112,
      	"codeName" : "WriteConflict",
      	"$clusterTime" : {
      		"clusterTime" : Timestamp(1524048246, 3),
      		"signature" : {
      			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
      			"keyId" : NumberLong(0)
      		}
      	}
      }
      

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: