[SERVER-41531] Support transactions on standalone instance Created: 05/Jun/19  Updated: 12/Sep/22  Resolved: 28/Jun/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Jarda Kotesovec Assignee: Eric Sedor
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-69517 moveChunk command fails with "Transac... Closed
is related to SERVER-30765 Don't allow txnNumbers in commands fo... Closed
is related to SERVER-35695 Enable transactions on inMemory stora... Closed
Participants:

 Description   

There is many use cases when standalone mongodb is much more suitable than replica-set. Typical use case is to run standalone mongodb per test file, ideally with memory storage. 



 Comments   
Comment by Eric Sedor [ 28/Jun/19 ]

Hi jarda.kotesovec;

I found SERVER-35695 which provides information about using transactions with the in-memory storage engine.

But I am closing this issue as transactions on standalone instances is something we've decided not to support.

Comment by Eric Sedor [ 06/Jun/19 ]

Hi jarda.kotesovec; Does a one node replica set running the inMemory storage engine work for your use-case? Transactions are supported in this topology.

EDIT: Apologies, Jarda, I misspoke. Transactions are supported on one-node replica sets with the wiredTiger storage engine.

Generated at Thu Feb 08 04:57:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.