[SERVER-38762] ephemeralForTest should support transactions Created: 22/Dec/18  Updated: 06/Dec/22  Resolved: 26/Apr/21

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

Type: Improvement Priority: Major - P3
Reporter: Oleg Pudeyev (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 1
Labels: EFT
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Storage Execution
Participants:

 Description   

I launched a 4.0 replica set with --storageEngine ephemeralForTest argument. The resulting replica set is much faster at running my tests, however it failed thusly on transactions tests:

     Mongo::Error::OperationFailure:
       Transaction numbers are only allowed on storage engines that support document-level locking (20)

This ticket is a request to support document level locking in ephemeralfortest storage engine, in order for it to be usable for transactions testing.



 Comments   
Comment by Connie Chen [ 26/Apr/21 ]

We have no plans to support users using ephemeralForTest.

Comment by Geert Bosch [ 10/Jun/20 ]

The ephemeralForTest storage engine is mainly intended for testing the database itself, most importantly in unit tests. If you want a fully functional version of MongoDB for your own application testing purposes and would like to avoid unnecessary I/O, you could run with WIredTIger on a memory-based filesystem, such as tmpfs.

Comment by Luis Pais [ 06/Jun/20 ]

Is there any progress for this ?
This is a real requirement for testing.

Comment by Oleg Pudeyev (Inactive) [ 03/Jan/19 ]

Instead of using the ephemeral storage engine I am now running mongodb on a zram partition. I don't know the relative performances of these but mongodb on zram is 2x faster than mongodb on nvme ssd.

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