Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Upgrade issue : Transaction numbers are only allowed on storage engines that support document-level locking

See original GitHub issue

bug?*

What is the current behavior?

After installing this morning the new version 5.7.0 (from 5.6.13) i’m now getting the following error on a until now perfectly working system

Transaction numbers are only allowed on storage engines that support document-level locking

must be linked to use MongoDB driver 3.3.x for MongoDB 4.2 support #8083 #8078

has this upgrade of the driver been tested ?

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:7

Top GitHub Comments

3reactions

givethemhellercommented, Sep 17, 2019

Yep - 3.7.x upgrades the the driver and turns on retryWrites automatically. Add ?retryWrites=false to end of connection string and you are square.

Ticket can be closed i think?

1reaction

vkarpov15commented, Dec 8, 2019

@LukeXF their response was to just disable retryWrites in the connection string. The rationale is that this change is to aid users of Atlas, which doesn’t support mmapv1.

Top Results From Across the Web

Transaction numbers are only allowed on storage engines ...

MongoError : Transaction numbers are only allowed on storage engines that support document-level locking #5983.

how to solve this transaction error in mlab? [MongoError

I'm using Ruby/Rails with MongoID, and I was having the same issue (Transaction numbers are only allowed on storage engines that support ......

[solved] Meteor 1.9.3+ and mongo document-level locking

After upgrading from 1.9 to 1.10.1, whenever I use the login, logout, or createUser methods, I get the following error:

Retryable Writes — MongoDB Manual

Supported Storage Engine : Retryable writes require a storage engine supporting document-level locking, such as the WiredTiger or in-memory storage engines.

MongoDB Transaction Management - Clairvoyant Blog

MongoDB uses optimistic updates for document-level concurrency and ... MongoDB uses WiredTiger Storage Engine to handle such issues.