[SERVER-40347] fix checks in optime.js for durable wall clock time and non-persistent storage engines Created: 26/Mar/19  Updated: 29/Oct/23  Resolved: 26/Mar/19

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

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2019-04-08
Participants:
Linked BF Score: 27

 Description   

optime.js was extended in SERVER-40080 to include checks on the durable wall clock times. However, the durable wall clock times may not have caught up when the test checks the replSetStatus output. Additionally, the test is not consistent in skipping the durable wall clock time checks across all non-persistent storage engines.



 Comments   
Comment by Githook User [ 26/Mar/19 ]

Author:

{'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}

Message: SERVER-40347 optime.js waits for durable wall clock times to synchronize across replica set nodes
Branch: master
https://github.com/mongodb/mongo/commit/6b5cfecb81da673a973415ada7c318865cf74153

Comment by Githook User [ 26/Mar/19 ]

Author:

{'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}

Message: SERVER-40347 optime.js determines storage engine support for persistence using server status
Branch: master
https://github.com/mongodb/mongo/commit/63f84d788b7fad7333064c3a2546254aad4dcfba

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