[SERVER-46524] ephemeralForTest cannot run new primary oplogTruncateAfterPoint updates because it does not support document level locking Created: 02/Mar/20  Updated: 29/Oct/23  Resolved: 03/Mar/20

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

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-45847 Pull the JournalFlusher out of the st... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-03-09
Participants:
Linked BF Score: 48

 Description   

ephemeralForTest does not support timestamps, nor does it do parallel writes on the primary, so there are no oplog holes. Therefore, we do not need the Replicate Before Journaling project changes to track oplog holes.



 Comments   
Comment by Githook User [ 03/Mar/20 ]

Author:

{'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@mongodb.com'}

Message: SERVER-46524 ephemeralForTest storage engine does not need to update the oplogTruncateAfterPoint when primary because there are no oplog holes (no parallel writes).

SERVER-46527 StorageInterfaceImpl::getLatestOplogTimestamp must have implementation logic supported
by all storage engines, not just WiredTiger.
Branch: master
https://github.com/mongodb/mongo/commit/0d5c66d73d0912f4d57c697a8fe491e827db0877

Generated at Thu Feb 08 05:11:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.