[SERVER-42453] ensure current clusterTime is greater than afterClusterTime value for read in step_down_on_secondary.js Created: 26/Jul/19  Updated: 29/Oct/23  Resolved: 29/Jul/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.2.1, 4.3.1

Type: Improvement Priority: Major - P3
Reporter: Pavithra Vetriselvan Assignee: Pavithra Vetriselvan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2
Participants:
Linked BF Score: 9

 Description   

In step_down_on_secondary.js, if we attempt to perform an afterClusterTime read at the timestamp greater than the current clusterTime, we will receive an error. We should make sure the clusterTime is advanced before performing this read.



 Comments   
Comment by Githook User [ 15/Aug/19 ]

Author:

{'name': 'Pavi Vetriselvan', 'email': 'pvselvan@umich.edu', 'username': 'pvselvan'}

Message: SERVER-42453 ensure clusterTime advances past afterClusterTime timestamp for read in step_down_on_secondary.js

(cherry picked from commit 4ae9ca6543819f7b6915b18ebf30e7633da78442)
Branch: v4.2
https://github.com/mongodb/mongo/commit/42c43501844112a29bcde40ac34b28c33298d2ab

Comment by Githook User [ 26/Jul/19 ]

Author:

{'name': 'Pavi Vetriselvan', 'username': 'pvselvan', 'email': 'pvselvan@umich.edu'}

Message: SERVER-42453 ensure clusterTime advances past afterClusterTime timestamp for read in step_down_on_secondary.js
Branch: master
https://github.com/mongodb/mongo/commit/4ae9ca6543819f7b6915b18ebf30e7633da78442

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