[SERVER-49425] Use clusterTime from oplog in 'change_streams_read_oplog_after_downgrade.js' Created: 10/Jul/20  Updated: 29/Oct/23  Resolved: 10/Jul/20

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

Type: Bug Priority: Major - P3
Reporter: Arun Banala Assignee: Arun Banala
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
Participants:
Linked BF Score: 15

 Description   

The current test code relies on the clusterTime returned by the insert command to be same as the time stamp written to the oplog. It looks like the clusterTime returned by the insert command is ahead of what is written in the oplog which is causing the test failure. Based on the oplog entires, it looks like there was a refresh on the collection.config.cache collection which incremented the clusterTime.

To fix this, we should read the time stamp from the oplog, instead of relying on the output of the insert command.



 Comments   
Comment by Githook User [ 10/Jul/20 ]

Author:

{'name': 'Arun Banala', 'email': 'arun.banala@mongodb.com', 'username': 'banarun'}

Message: SERVER-49425 Use clusterTime from oplog in 'change_streams_read_oplog_after_downgrade.js'
Branch: master
https://github.com/mongodb/mongo/commit/b937b31a60d6f62c68329bb05fc0b5bfacd17217

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